servicos.acesso.gov.br speed test — 20 Oct 2026

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

https://servicos.acesso.gov.br/

20 October 2026 at 12:41 UTC · Free test · report pt_562ebdd14e35
Grade
C
75/100
Performance77/100
Structure73/100

10 audit(s) passed, 6 need work

First byte (TTFB)1.01 smeasured from this server
Fully loaded1.80 sfirst byte + slowest asset
Requests7document + assets
Page weight899.5 KBcompressed transfer
HTML document924 Bno compression
ProtocolHTTP/3openresty/1.31.1.1
Third-party18.7 KBother hosts

Where the first byte went

  • DNS lookup 414 ms 41%
  • TCP connect 181 ms 18%
  • Server wait 413 ms 41%

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 86% of 4,999 pages tested here1.01 s against a median of 448 ms
Page weightheavier than 59% of 4,999 pages tested here899.5 KB against a median of 650.3 KB
Fully loadedfaster than 52% of 4,999 pages tested here1.80 s against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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 1.01 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 899.5 KB over 7 request(s), which is lean. Javascript files are 85% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.

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 servicos.acesso.gov.br
Mobile 390 × 844 · 7.5 KB · page is 844 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 paintnot reportedgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paintnot reportedfirst content on screen
Browser page weight1.15 MB21 request(s), scripts included
Largest contentful paintnot reported
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 1 request
764.5 KB 85%
Css 4 requests
132.0 KB 15%
Images 1 request
2.1 KB 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1009 ms. Of that, 413 ms was the server thinking and 595 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.

Render-blocking resources

high impact

5 render-blocking resource(s) in the document head (1 script(s), 4 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

medium impact

The page transfers 899.5 KB across 7 request(s), with the document itself at 924 B.

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

Cache static assets

medium impact

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

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: index-D8_Oslqc.js (764.5 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Waterfall

Slowest requests

CSSservicos.acesso.gov.br/styles/portal_logado.css
788 ms
IMAGESservicos.acesso.gov.br/favicon.ico
735 ms
JAVASCRIPTservicos.acesso.gov.br/assets/index-D8_Oslqc.js
728 ms
CSSservicos.acesso.gov.br/assets/index-BEgTv0L5.css
709 ms
CSScdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.0/css/all.m…
393 ms
CSSfonts.googleapis.com/css
363 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://servicos.acesso.gov.br/styles/portal_logado.csscss200788 ms540 B
https://servicos.acesso.gov.br/favicon.icoimages200735 ms2.1 KB
https://servicos.acesso.gov.br/assets/index-D8_Oslqc.jsjavascript200728 ms764.5 KB
https://servicos.acesso.gov.br/assets/index-BEgTv0L5.csscss200709 ms112.8 KB
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.0/css/all.min.css 3rd partycss200393 ms18.4 KB
https://fonts.googleapis.com/css?family=Raleway:300,400,500,600,700,800,900&display=swap 3rd partycss200363 ms253 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.