www.computrabajo.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:49 UTC. Grade A (91/100), with the screenshots, the timings and the fixes that matter.

https://www.computrabajo.com/

20 October 2026 at 14:49 UTC · Free test · report pt_4cab4bae8bab
Grade
A
91/100
Performance95/100
Structure85/100

12 audit(s) passed, 4 need work

First byte (TTFB)404 msmeasured from this server
Fully loaded1.02 sfirst byte + slowest asset
Requests8document + assets
Page weight83.4 KBcompressed transfer
HTML document7.8 KBgzip
ProtocolHTTP/3Microsoft-IIS/10.0
Third-party92 Bother hosts

Where the first byte went

  • DNS lookup 55 ms 14%
  • TCP connect 77 ms 19%
  • Server wait 272 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 56% of 4,999 pages tested here404 ms against a median of 449 ms
Page weightlighter than 89% of 4,999 pages tested here83.4 KB against a median of 650.5 KB
Fully loadedfaster than 92% of 4,999 pages tested here1.02 s against a median of 1.84 s
Requestssends fewer requests than 90% of 4,999 pages tested here8 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 404 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 83.4 KB over 8 request(s), which is lean. Javascript files are 56% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • 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 532 ms, inside the 2.5 s Google calls good.

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 www.computrabajo.com
Mobile 390 × 844 · 52.2 KB · page is 2195 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 paint532 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint396 msfirst content on screen
Browser page weight304.0 KB15 request(s), scripts included
Largest contentful paint532 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests
46.6 KB 56%
Images 3 requests
25.4 KB 30%
Css 1 request
3.5 KB 4%
Html 1 request
92 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 404 ms. Of that, 272 ms was the server thinking and 132 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

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

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

IMAGESwww.computrabajo.com/img/logoct_neg.svg
612 ms
CSSwww.computrabajo.com/css/ct.css
577 ms
IMAGESwww.computrabajo.com/img/mapahomect.jpg
569 ms
JAVASCRIPTwww.computrabajo.com/js/web.js
532 ms
JAVASCRIPTwww.computrabajo.com/js/jquery.js
510 ms
IMAGESwww.computrabajo.com/img/favicon_ct.svg
497 ms
HTMLwww.googletagmanager.com/ns.html
432 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.computrabajo.com/img/logoct_neg.svgimages200612 ms1.5 KB
https://www.computrabajo.com/css/ct.css?v9css200577 ms3.5 KB
https://www.computrabajo.com/img/mapahomect.jpgimages200569 ms22.3 KB
https://www.computrabajo.com/js/web.js?v8javascript200532 ms2.1 KB
https://www.computrabajo.com/js/jquery.jsjavascript200510 ms44.5 KB
https://www.computrabajo.com/img/favicon_ct.svgimages200497 ms1.6 KB
https://www.googletagmanager.com/ns.html?id=GTM-NZGBV7Z 3rd partyhtml200432 ms92 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.