languagetool.org speed test — 20 Oct 2026

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

https://languagetool.org/

20 October 2026 at 16:16 UTC · Free test · report pt_b08f123dbdd6
Grade
C
71/100
Performance70/100
Structure73/100

10 audit(s) passed, 6 need work

First byte (TTFB)1.11 smeasured from this server
Fully loaded2.50 sfirst byte + slowest asset
Requests26document + assets
Page weight1.13 MBcompressed transfer
HTML document21.1 KBbr
ProtocolHTTP/3cloudflare

Where the first byte went

  • DNS lookup 95 ms 9%
  • TCP connect 18 ms 2%
  • Server wait 994 ms 90%

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 89% of 4,999 pages tested here1.11 s against a median of 448 ms
Page weightheavier than 66% of 4,999 pages tested here1.13 MB against a median of 650.3 KB
Fully loadedslower than 74% of 4,999 pages tested here2.50 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 1.11 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 1.13 MB over 26 request(s). Javascript files are 72% 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.

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

Javascript 5 requests
826.9 KB 72%
Images 17 requests
215.1 KB 19%
Css 3 requests
89.3 KB 8%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1107 ms. Of that, 994 ms was the server thinking and 113 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

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.

Total page weight

medium impact

The page transfers 1.13 MB across 26 request(s), with the document itself at 21.1 KB.

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

JavaScript weight

medium impact

2 JavaScript file(s) over 200 KB: app-en.js (221.4 KB), languagetool-en-external-react.js (431.3 KB)

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

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

IMAGESlanguagetool.org/images/favicons/apple-touch-icon-72x72…
1.40 s
IMAGESlanguagetool.org/images/examples/example_en_style.png
1.12 s
IMAGESlanguagetool.org/images/examples/example_en_rephrasing.png
1.10 s
IMAGESlanguagetool.org/images/examples/example_en_grammar.png
1.09 s
IMAGESlanguagetool.org/images/examples/example_en_casing.png
1.09 s
IMAGESlanguagetool.org/images/examples/example_en_spelling.png
1.09 s
IMAGESlanguagetool.org/images/favicons/apple-touch-icon-76x76…
1.08 s
IMAGESlanguagetool.org/images/favicons/apple-touch-icon-60x60…
1.07 s
CSSlanguagetool.org/css/website.css
1.00 s
CSSlanguagetool.org/css/base.css
970 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://languagetool.org/images/favicons/apple-touch-icon-72x72.pngimages2001.40 s789 B
https://languagetool.org/images/examples/example_en_style.pngimages2001.12 s32.8 KB
https://languagetool.org/images/examples/example_en_rephrasing.pngimages2001.10 s27.1 KB
https://languagetool.org/images/examples/example_en_grammar.pngimages2001.09 s38.7 KB
https://languagetool.org/images/examples/example_en_casing.pngimages2001.09 s33.8 KB
https://languagetool.org/images/examples/example_en_spelling.pngimages2001.09 s29.9 KB
https://languagetool.org/images/favicons/apple-touch-icon-76x76.pngimages2001.08 s817 B
https://languagetool.org/images/favicons/apple-touch-icon-60x60.pngimages2001.07 s688 B
https://languagetool.org/css/website.css?id=3ab74021cf6eedc68d5b230dc1aac499css2001.00 s40.7 KB
https://languagetool.org/css/base.css?id=63d7085543a4f41bfed4b44a4d01b40bcss200970 ms48.0 KB
https://languagetool.org/images/favicons/apple-touch-icon-180x180.pngimages200959 ms1.4 KB
https://languagetool.org/images/favicons/apple-touch-icon-144x144.pngimages200949 ms1.1 KB
https://languagetool.org/images/examples/example_en_punctuation.pngimages200945 ms43.3 KB
https://languagetool.org/js/_new/react.bundle.js?id=92b30eef365a8af9c016d47c11076d61javascript200943 ms69.4 KB
https://languagetool.org/js/_new/manifest.js?id=9f5bba01f0bcf2e73d18f6153980e166javascript200938 ms3.1 KB
https://languagetool.org/images/favicons/apple-touch-icon-152x152.pngimages200928 ms1.2 KB
https://languagetool.org/images/favicons/favicon-16x16.pngimages200926 ms367 B
https://languagetool.org/images/favicons/apple-touch-icon-120x120.pngimages200925 ms1.0 KB
https://languagetool.org/images/favicons/favicon-32x32.pngimages200924 ms501 B
https://languagetool.org/images/favicons/apple-touch-icon-114x114.pngimages200917 ms1.0 KB
https://languagetool.org/js/_new/app-en.js?id=d113b2aae106f9ced7265ed0d2729285javascript200904 ms221.4 KB
https://languagetool.org/js/_new/chunks/standalone-styles.js?id=5ee50d33e7792089javascript200904 ms101.7 KB
https://languagetool.org/css/print.css?id=24330adae585d3b6b8b10284aaaf9417css200904 ms634 B
https://languagetool.org/js/_new/chunks/languagetool-en-external-react.js?id=c20b760eb98dcf52javascript200903 ms431.3 KB
https://languagetool.org/images/favicons/apple-touch-icon-57x57.pngimages200903 ms720 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.