www.erome.com speed test — 20 Oct 2026

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

https://www.erome.com/

20 October 2026 at 12:29 UTC · Free test · report pt_98eb8e7c4ff6
Grade
A
96/100
Performance97/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)295 msmeasured from this server
Fully loaded935 msfirst byte + slowest asset
Requests16document + assets
Page weight363.6 KBcompressed transfer
HTML document4.1 KBbr
ProtocolHTTP/3BunnyCDN-IL1-1346
Third-party238.7 KBother hosts

Where the first byte went

  • DNS lookup 48 ms 16%
  • TCP connect 59 ms 20%
  • Server wait 188 ms 64%

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 75% of 4,999 pages tested here295 ms against a median of 449 ms
Page weightlighter than 67% of 4,999 pages tested here363.6 KB against a median of 650.5 KB
Fully loadedfaster than 93% of 4,999 pages tested here935 ms against a median of 1.84 s
Requestssends fewer requests than 83% of 4,999 pages tested here16 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 295 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 363.6 KB over 16 request(s). Javascript files are 80% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 66% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 792 ms, inside the 2.5 s Google calls good.

Fix first: Render-blocking resources - 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.

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.erome.com
Mobile 390 × 844 · 42.6 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 paint792 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 paint768 msfirst content on screen
Browser page weight391.8 KB13 request(s), scripts included
Largest contentful paint792 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 5 requests
291.3 KB 80%
Images 6 requests
37.3 KB 10%
Css 3 requests
30.8 KB 8%
Other 1 request
200 B 0%

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

Top issues

Render-blocking resources

high impact

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

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

CSSwww.erome.com/css/app.css
640 ms
JAVASCRIPTwww.erome.com/js/libraries.js
639 ms
CSSwww.erome.com/css/libraries.css
637 ms
JAVASCRIPTwww.erome.com/js/main.js
630 ms
IMAGESwww.erome.com/img/logo-erome-vertical.png
628 ms
IMAGESwww.erome.com/apple-touch-icon.png
625 ms
IMAGESwww.erome.com/img/bg.jpg
620 ms
JAVASCRIPTcdn.tsyndicate.com/sdk/v1/n.js
618 ms
OTHERwww.erome.com/manifest.json
613 ms
IMAGESwww.erome.com/favicon-32x32.png
596 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.erome.com/css/app.css?v=4.59css200640 ms12.4 KB
https://www.erome.com/js/libraries.js?v=6.4javascript200639 ms46.7 KB
https://www.erome.com/css/libraries.css?v=4css200637 ms18.2 KB
https://www.erome.com/js/main.js?v=2.72javascript200630 ms6.1 KB
https://www.erome.com/img/logo-erome-vertical.pngimages200628 ms2.1 KB
https://www.erome.com/apple-touch-icon.pngimages200625 ms2.9 KB
https://www.erome.com/img/bg.jpgimages200620 ms26.2 KB
https://cdn.tsyndicate.com/sdk/v1/n.js 3rd partyjavascript200618 ms23.5 KB
https://www.erome.com/manifest.jsonother200613 ms200 B
https://www.erome.com/favicon-32x32.pngimages200596 ms1.1 KB
https://www.googletagmanager.com/gtag/js?id=G-6S5PBWQ8CG 3rd partyjavascript200594 ms155.9 KB
https://a.magsrv.com/ad-provider.js 3rd partyjavascript200594 ms59.2 KB
https://fonts.googleapis.com/css?family=Montserrat&display=swap 3rd partycss200594 ms206 B
https://www.erome.com/android-chrome-192x192.pngimages200593 ms4.1 KB
https://www.erome.com/favicon-16x16.pngimages200593 ms765 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.