www.jennymovies.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 15:35 UTC. Grade B (86/100), with the screenshots, the timings and the fixes that matter.

https://www.jennymovies.com/

20 October 2026 at 15:35 UTC · Free test · report pt_21fa5a82e643
Grade
B
86/100
Performance85/100
Structure88/100

13 audit(s) passed, 3 need work

First byte (TTFB)665 msmeasured from this server
Fully loaded2.22 sfirst byte + slowest asset
Requests13document + assets
Page weight171.7 KBcompressed transfer
HTML document8.0 KBbr
ProtocolHTTP/3Angie
Third-party53.6 KBother hosts

Where the first byte went

  • DNS lookup 95 ms 14%
  • TCP connect 170 ms 26%
  • Server wait 400 ms 60%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First byteslower than 67% of 4,999 pages tested here665 ms against a median of 448 ms
Page weightlighter than 81% of 4,999 pages tested here171.7 KB against a median of 650.5 KB
Fully loadedslower than 65% of 4,999 pages tested here2.22 s against a median of 1.84 s
Requestssends fewer requests than 85% of 4,999 pages tested here13 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte took 665 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 171.7 KB over 13 request(s), which is lean. Images files are 41% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 31% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 1.84 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 17 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint1.84 sgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking time17 mslong tasks during load
First contentful paint1.18 sfirst content on screen
Browser page weight879.7 KB41 request(s), scripts included
Largest contentful paint1.84 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking time17 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 5 requests
70.2 KB 41%
Javascript 3 requests
59.3 KB 35%
Fonts 2 requests
26.4 KB 15%
Css 1 request
7.1 KB 4%
Other 1 request
649 B 0%

Transfer size, compressed as sent. 13 request(s) in total, 171.7 KB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 665 ms. Of that, 400 ms was the server thinking and 265 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Cache static assets

medium impact

5 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Waterfall

Slowest requests

FONTSwww.jennymovies.com/fonts/Montserrat-Regular.woff2
1.55 s
FONTSwww.jennymovies.com/fonts/icons.woff2
1.49 s
JAVASCRIPTcss.jennymovies.com/jennymovies.js
1.02 s
IMAGESwww.jennymovies.com/jennymoviesm.svg
977 ms
JAVASCRIPTwww.jennymovies.com/atguulqxb/qluyxqpx/dbpksqvmi.js
977 ms
CSSwww.jennymovies.com/jennymovies.css
936 ms
OTHERwww.jennymovies.com/site.webmanifest
905 ms
IMAGESwww.jennymovies.com/favicon.ico
852 ms
IMAGESwww.jennymovies.com/apple-touch-icon.png
848 ms
IMAGESwww.jennymovies.com/favicon-16x16.png
848 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.jennymovies.com/fonts/Montserrat-Regular.woff2fonts2001.55 s21.0 KB
https://www.jennymovies.com/fonts/icons.woff2fonts2001.49 s5.4 KB
https://css.jennymovies.com/jennymovies.js?v=1792492508 3rd partyjavascript2001.02 s23.1 KB
https://www.jennymovies.com/jennymoviesm.svgimages200977 ms61.0 KB
https://www.jennymovies.com/atguulqxb/qluyxqpx/dbpksqvmi.jsjavascript200977 ms5.7 KB
https://www.jennymovies.com/jennymovies.css?v=1792492508css200936 ms7.1 KB
https://www.jennymovies.com/site.webmanifestother200905 ms649 B
https://www.jennymovies.com/favicon.icoimages200852 ms2.3 KB
https://www.jennymovies.com/apple-touch-icon.pngimages200848 ms5.1 KB
https://www.jennymovies.com/favicon-16x16.pngimages200848 ms701 B
https://www.jennymovies.com/favicon-32x32.pngimages200845 ms1.1 KB
https://ajax.googleapis.com/ajax/libs/jquery/3.6.4/jquery.min.js 3rd partyjavascript200721 ms30.4 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.