emojicombos.com speed test — 20 Oct 2026

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

https://emojicombos.com/

20 October 2026 at 16:04 UTC · Free test · report pt_9f6454ceba08
Grade
A
96/100
Performance96/100
Structure97/100

15 audit(s) passed, 1 need work

First byte (TTFB)333 msmeasured from this server
Fully loaded712 msfirst byte + slowest asset
Requests5document + assets
Page weight191.3 KBcompressed transfer
HTML document2.3 KBzstd
ProtocolHTTP/3cloudflare
Third-party166.2 KBother hosts

Where the first byte went

  • DNS lookup 88 ms 26%
  • TCP connect 64 ms 19%
  • Server wait 181 ms 54%

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 68% of 4,999 pages tested here333 ms against a median of 449 ms
Page weightlighter than 80% of 4,999 pages tested here191.3 KB against a median of 650.5 KB
Fully loadedfaster than 96% of 4,999 pages tested here712 ms against a median of 1.84 s
Requestssends fewer requests than 93% of 4,999 pages tested here5 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 333 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 191.3 KB over 5 request(s), which is lean. Javascript files are 87% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives zstd-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 87% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element took 5.52 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.

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

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 emojicombos.com
Mobile 390 × 844 · 23.0 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 paint5.52 sgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint5.52 sfirst content on screen
Browser page weight395.7 KB11 request(s), scripts included
Largest contentful paint5.52 s
Poorgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
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
166.0 KB 87%
Images 1 request
22.6 KB 12%
Css 1 request
245 B 0%
Other 1 request
190 B 0%

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

Top issues

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

JAVASCRIPTwww.googletagmanager.com/gtag/js
379 ms
CSSfonts.googleapis.com/css
332 ms
OTHERemojicombos.com/manifest.json
323 ms
IMAGESemojicombos.com/heavy-plus-sign_2795.png
295 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.googletagmanager.com/gtag/js?id=G-WF5V0J3NPY 3rd partyjavascript200379 ms166.0 KB
https://fonts.googleapis.com/css?family=Roboto:400,700&display=swap 3rd partycss200332 ms245 B
https://emojicombos.com/manifest.jsonother200323 ms190 B
https://emojicombos.com/heavy-plus-sign_2795.pngimages200295 ms22.6 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.