clickpetroleoegas.com.br speed test — 20 Oct 2026

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

https://clickpetroleoegas.com.br/

20 October 2026 at 13:02 UTC · Free test · report pt_02b89b3ef15e

Re-test this page Test your own site

Grade

84/100

Performance85/100

Structure82/100

13 audit(s) passed, 3 need work

First byte (TTFB)703 msmeasured from this server

Fully loaded1.77 sfirst byte + slowest asset

Requests26document + assets

Page weight556.8 KBcompressed transfer

HTML document75.0 KBbr

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 68 ms 10%
TCP connect 23 ms 3%
Server wait 612 ms 87%

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 70% of 4,999 pages tested here703 ms against a median of 448 ms

Page weightlighter than 55% of 4,999 pages tested here556.8 KB against a median of 650.5 KB

Fully loadedfaster than 54% of 4,999 pages tested here1.77 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 703 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 556.8 KB over 26 request(s). Images files are 87% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
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.

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

481.9 KB 87%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 703 ms. Of that, 612 ms was the server thinking and 91 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

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

Render-blocking resources

high impact

4 render-blocking resource(s) in the document head (0 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.