paramount.tech speed test — 20 Oct 2026

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

https://paramount.tech/

20 October 2026 at 15:09 UTC · Free test · report pt_e0ef59fbad87
Grade
D
62/100
Performance58/100
Structure67/100

10 audit(s) passed, 6 need work

First byte (TTFB)737 msmeasured from this server
Fully loaded2.06 sfirst byte + slowest asset
Requests26document + assets
Page weight6.68 MBcompressed transfer
HTML document7.8 KBgzip
ProtocolHTTP/3nginx
Third-party9.0 KBother hosts

Where the first byte went

  • DNS lookup 60 ms 8%
  • TCP connect 69 ms 9%
  • Server wait 608 ms 82%

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 72% of 4,999 pages tested here737 ms against a median of 448 ms
Page weightheavier than 95% of 4,999 pages tested here6.68 MB against a median of 650.3 KB
Fully loadedslower than 59% of 4,999 pages tested here2.06 s against a median of 1.84 s
Requestssends more requests than 100% of 4,999 pages tested here26 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 737 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 6.68 MB over 26 request(s). Images files are 99% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 752 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 219 ms, so taps and scrolling wait while scripts run.

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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of paramount.tech
Mobile 390 × 844 · 202.9 KB · page is 5013 px tall

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 paint752 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time219 mslong tasks during load
First contentful paint752 msfirst content on screen
Browser page weight8.08 MB41 request(s), scripts included
Largest contentful paint752 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time219 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 19 requests
6.58 MB 99%
Javascript 3 requests
58.9 KB 1%
Css 3 requests
31.1 KB 0%

Transfer size, compressed as sent. 26 request(s) in total, 6.68 MB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 737 ms. Of that, 608 ms was the server thinking and 129 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.

Image delivery and format

high impact

7 image(s) over 200 KB and 11 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (0 script(s), 3 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

high impact

The page transfers 6.68 MB across 26 request(s), with the document itself at 7.8 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Cache static assets

medium impact

23 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.

Waterfall

Slowest requests

CSSfonts.googleapis.com/css
1.32 s
IMAGESparamount.tech/assets/img/portfolio/awkwardpage.png
1.30 s
IMAGESparamount.tech/assets/img/twitter-32.png
1.30 s
IMAGESparamount.tech/assets/img/portfolio/vivaclubcharts.jpg
1.28 s
IMAGESparamount.tech/assets/img/portfolio/mtv_apps.png
1.27 s
IMAGESparamount.tech/assets/img/linkedin-32.png
1.27 s
IMAGESparamount.tech/assets/img/portfolio/south_park.jpeg
1.27 s
IMAGESparamount.tech/assets/img/facebook-32.png
1.27 s
IMAGESparamount.tech/assets/img/portfolio/mtv.com.png
1.26 s
IMAGESparamount.tech/assets/img/portfolio/www.comedycentral…
1.26 s

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://fonts.googleapis.com/css?family=Lato:400,300,700,300italic,400italic 3rd partycss2001.32 s237 B
https://paramount.tech/assets/img/portfolio/awkwardpage.pngimages2001.30 s320.4 KB
https://paramount.tech/assets/img/twitter-32.pngimages2001.30 s721 B
https://paramount.tech/assets/img/portfolio/vivaclubcharts.jpgimages2001.28 s87.1 KB
https://paramount.tech/assets/img/portfolio/mtv_apps.pngimages2001.27 s811.0 KB
https://paramount.tech/assets/img/linkedin-32.pngimages2001.27 s565 B
https://paramount.tech/assets/img/portfolio/south_park.jpegimages2001.27 s139.7 KB
https://paramount.tech/assets/img/facebook-32.pngimages2001.27 s721 B
https://paramount.tech/assets/img/portfolio/mtv.com.pngimages2001.26 s1.08 MB
https://paramount.tech/assets/img/portfolio/www.comedycentral.pl.pngimages2001.26 s842.8 KB
https://paramount.tech/assets/img/portfolio/www.cc.com.pngimages2001.25 s1.07 MB
https://paramount.tech/assets/img/portfolio/Twitter_Page_mtvpolska.pngimages2001.25 s429.8 KB
https://paramount.tech/assets/img/bg/life_at_paramount_v5.pngimages2001.25 s87.3 KB
https://paramount.tech/assets/img/portfolio/insights.paramount.com.pngimages2001.24 s1.23 MB
https://paramount.tech/assets/img/join_our_team_v2.pngimages2001.24 s169.7 KB
https://paramount.tech/assets/img/portfolio/awkwardpage-350x233.pngimages2001.24 s133.9 KB
https://paramount.tech/assets/img/bg/agile_banner_v4.pngimages2001.24 s111.7 KB
https://paramount.tech/assets/img/portfolio/nickelodeaon_orange_bg.jpegimages2001.24 s88.0 KB
https://paramount.tech/assets/js/main.jsjavascript2001.24 s49.9 KB
https://paramount.tech/assets/img/jekyll-logo-2x.pngimages2001.24 s44.9 KB
https://paramount.tech/assets/css/main.css?v=202608261707css2001.24 s30.2 KB
https://paramount.tech/assets/img/paramount_skydance_logo_navy.pngimages2001.24 s16.6 KB
https://cdn.privacy.paramount.com/dist/optanon-v2.0.0.js 3rd partyjavascript2001.24 s8.8 KB
https://paramount.tech/assets/css/share-article-btn.css?v=202608261707css2001.24 s669 B
https://paramount.tech/assets/js/copyrightYear.jsjavascript2001.24 s140 B
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.