www.record.pt speed test — 20 Oct 2026

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

https://www.record.pt/

20 October 2026 at 15:37 UTC · Free test · report pt_1aff47067b57
Grade
B
80/100
Performance79/100
Structure82/100

11 audit(s) passed, 5 need work

First byte (TTFB)878 msmeasured from this server
Fully loaded2.29 sfirst byte + slowest asset
Requests26document + assets
Page weight703.9 KBcompressed transfer
HTML document366.3 KBgzip
ProtocolHTTP/2Microsoft-IIS/10.0
Third-party277.0 KBother hosts

Where the first byte went

  • DNS lookup 75 ms 9%
  • TCP connect 213 ms 24%
  • Server wait 590 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 byteslower than 80% of 4,999 pages tested here878 ms against a median of 448 ms
Page weightheavier than 52% of 4,999 pages tested here703.9 KB against a median of 650.3 KB
Fully loadedslower than 68% of 4,999 pages tested here2.29 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 878 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 703.9 KB over 26 request(s). Images files are 48% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • 39% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Images 25 requests
337.6 KB 48%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 878 ms. Of that, 590 ms was the server thinking and 288 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

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

Third-party weight

medium impact

2 third-party host(s) serve 277.0 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

HTML document size

medium impact

The document transfers 366.3 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

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

IMAGESpubs.xl.pt/bate_coracao.gif
1.42 s
IMAGEScdn.record.pt/images/2026-08/img_293x165uu2026-08-14…
1.37 s
IMAGESpubs.xl.pt/Corrida-Sao-Silvestre_advance-care_300…
1.36 s
IMAGEScdn.record.pt/images//2026-10/img_476x268uu2026-10-2…
1.31 s
IMAGEScdn.record.pt/images/2026-04/img_476x268uu2026-04-06…
1.30 s
IMAGESwww.record.pt/staticassets/passatempos_barra/i/pm.png
1.27 s
IMAGESwww.record.pt/staticassets/passatempos_barra/i/pd.png
1.24 s
IMAGEScdn.record.pt/images/2026-10/img_80x100uu2026-10-20-…
1.23 s
IMAGEScdn.record.pt/images/2015-11/img_84x84uu2015-11-20-1…
1.22 s
IMAGEScdn.record.pt/images/2015-10/img_84x84uu2015-10-02-1…
1.22 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://pubs.xl.pt/bate_coracao.gif 3rd partyimages2001.42 s65.2 KB
https://cdn.record.pt/images/2026-08/img_293x165uu2026-08-14-09-58-21-2456993.jpg 3rd partyimages2001.37 s15.0 KB
https://pubs.xl.pt/Corrida-Sao-Silvestre_advance-care_300x80.gif 3rd partyimages2001.36 s39.6 KB
https://cdn.record.pt/images//2026-10/img_476x268uu2026-10-20-13-53-52-2469345-im-639281012535322315.jpg 3rd partyimages2001.31 s22.8 KB
https://cdn.record.pt/images/2026-04/img_476x268uu2026-04-06-18-46-04-2431420.jpg 3rd partyimages2001.30 s17.6 KB
https://www.record.pt/staticassets/passatempos_barra/i/pm.pngimages2001.27 s9.1 KB
https://www.record.pt/staticassets/passatempos_barra/i/pd.pngimages2001.24 s33.7 KB
https://cdn.record.pt/images/2026-10/img_80x100uu2026-10-20-01-08-00-2469289.jpg 3rd partyimages2001.23 s4.4 KB
https://cdn.record.pt/images/2015-11/img_84x84uu2015-11-20-14-07-28-1007546.png 3rd partyimages2001.22 s8.1 KB
https://cdn.record.pt/images/2015-10/img_84x84uu2015-10-02-17-27-29-1005619.png 3rd partyimages2001.22 s12.3 KB
https://cdn.record.pt/images//2024-08/img_84x84uu2024-08-28-20-00-27-2289505.png 3rd partyimages2001.22 s15.6 KB
https://cdn.record.pt/images//2024-08/img_84x84uu2026-07-24-15-25-12-2289493.png 3rd partyimages2001.22 s9.3 KB
https://cdn.record.pt/images/2015-10/img_84x84uu2015-10-05-13-35-14-1005643.png 3rd partyimages2001.21 s3.9 KB
https://cdn.record.pt/images/2021-08/img_84x84uu2021-08-28-02-06-30-1896284.png 3rd partyimages2001.21 s10.3 KB
https://www.record.pt/i/logo_esc.pngimages2001.21 s1.7 KB
https://www.record.pt/i/clock.svgimages2001.20 s1.6 KB
https://www.record.pt/novo-record/i/logos/logo-liga-record.svgimages2001.20 s5.4 KB
https://www.record.pt/novo-record/i/logos/logo-record-branco.svgimages2001.20 s4.4 KB
https://www.record.pt/novo-record/i/icons/icon-iniciativas.svgimages2001.20 s4.2 KB
https://cdn.record.pt/images//2026-01/img_84x84uu2026-01-14-20-22-01-2414756.png 3rd partyimages2001.20 s7.4 KB
https://www.record.pt/novo-record/i/icons/icon-email.svgimages2001.20 s481 B
https://cdn.record.pt/images/2016-02/img_40x40uu2016-02-03-04-05-14-1059807.png 3rd partyimages2001.17 s3.7 KB
https://cdn.record.pt/images/2024-10/img_40x40uu2024-10-01-12-20-02-2299075.png 3rd partyimages2001.14 s3.3 KB
https://cdn.record.pt/images/2026-10/img_293x165uu2026-10-20-14-28-04-2469349.jpg 3rd partyimages2001.13 s19.3 KB
https://cdn.record.pt/images/2026-10/img_293x165uu2026-10-20-14-12-18-2469347.jpg 3rd partyimages2001.13 s19.3 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.