sketchup.trimble.com/en speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:47 UTC. Grade C (76/100), with the screenshots, the timings and the fixes that matter.

https://sketchup.trimble.com/en

20 October 2026 at 13:47 UTC · Free test · report pt_e4a54b19befc

Re-test this page Test your own site

Grade

76/100

Performance74/100

Structure80/100

12 audit(s) passed, 4 need work

First byte (TTFB)392 msmeasured from this server

Fully loaded3.49 sfirst byte + slowest asset

Requests26document + assets

Page weight2.46 MBcompressed transfer

HTML document316.5 KBgzip

ProtocolHTTP/3Netlify

Third-party214.1 KBother hosts

Where the first byte went

DNS lookup 69 ms 18%
TCP connect 61 ms 16%
Server wait 261 ms 67%

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 bytefaster than 58% of 4,999 pages tested here392 ms against a median of 449 ms

Page weightheavier than 85% of 4,999 pages tested here2.46 MB against a median of 650.3 KB

Fully loadedslower than 86% of 4,999 pages tested here3.49 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 arrived in 392 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 2.46 MB over 26 request(s). Html files are 79% of it, so that one type is worth a look on its own.
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 624 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.011), so nothing jumps under the reader's cursor.
The main thread was blocked for 166 ms in total, which is not enough to feel.

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

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 sketchup.trimble.com — **Mobile** 390 × 844 · 199.4 KB · page is 6000 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 paint624 msgood is under 2.5 s

Cumulative layout shift0.011under 0.1 is stable

Total blocking time166 mslong tasks during load

First contentful paint588 msfirst content on screen

Browser page weight3.50 MB168 request(s), scripts included

Failed requests9blocked or unreachable

Largest contentful paint624 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.011

Goodgood under 0.1, poor over 0.25

Total blocking time166 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 23 requests

1.94 MB 79%

Images 2 requests

214.1 KB 9%

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

Top issues

Total page weight

high impact

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

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

Image delivery and format

medium impact

0 image(s) over 200 KB and 2 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.

HTML document size

medium impact

The document transfers 316.5 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

Avoid extra redirects

medium impact

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