ollama.com speed test — 20 Oct 2026

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

https://ollama.com/

20 October 2026 at 13:56 UTC · Free test · report pt_b48040d693eb
Grade
A
90/100
Performance95/100
Structure83/100

12 audit(s) passed, 4 need work

First byte (TTFB)403 msmeasured from this server
Fully loaded1.48 sfirst byte + slowest asset
Requests24document + assets
Page weight244.7 KBcompressed transfer
HTML document15.9 KBno compression
ProtocolHTTP/3Google Frontend

Where the first byte went

  • DNS lookup 82 ms 20%
  • TCP connect 68 ms 17%
  • Server wait 253 ms 63%

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 56% of 4,999 pages tested here403 ms against a median of 449 ms
Page weightlighter than 76% of 4,999 pages tested here244.7 KB against a median of 650.5 KB
Fully loadedfaster than 72% of 4,999 pages tested here1.48 s against a median of 1.84 s
Requestssends fewer requests than 76% of 4,999 pages tested here24 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 403 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 244.7 KB over 24 request(s). Css files are 36% of it, so split the stylesheet so the first screen does not download the whole site.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 504 ms, inside the 2.5 s Google calls good.

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 ollama.com
Mobile 390 × 844 · 36.9 KB · page is 1000 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 paint504 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 paint488 msfirst content on screen
Browser page weight213.2 KB17 request(s), scripts included
Largest contentful paint504 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

Css 2 requests
88.3 KB 36%
Javascript 1 request
87.6 KB 36%
Images 18 requests
29.2 KB 12%
Html 2 requests
23.8 KB 10%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 403 ms. Of that, 253 ms was the server thinking and 150 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.

Compress text responses

high impact

2 text response(s) of 10 KB or more are sent uncompressed, and the document itself is compressed. That is 174.1 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Render-blocking resources

high impact

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

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

CSSollama.com/public/vendor/prism/prism.css
1.07 s
CSSollama.com/public/tailwind.css
1.05 s
IMAGESollama.com/public/logos/nvidia.svg
1.04 s
IMAGESollama.com/public/ollama-nav.png
1.00 s
IMAGESollama.com/public/apple-touch-icon.png
995 ms
IMAGESollama.com/public/icon-64x64.png
995 ms
IMAGESollama.com/public/icon-48x48.png
993 ms
IMAGESollama.com/public/icon-16x16.png
989 ms
JAVASCRIPTollama.com/public/vendor/htmx/bundle.js
987 ms
IMAGESollama.com/public/logos/mercedes.svg
986 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://ollama.com/public/vendor/prism/prism.css?v=4a172e82af6a0d20aea36aaf508c4cc4css2001.07 s1.8 KB
https://ollama.com/public/tailwind.css?v=4a172e82af6a0d20aea36aaf508c4cc4css2001.05 s86.5 KB
https://ollama.com/public/logos/nvidia.svgimages2001.04 s2.6 KB
https://ollama.com/public/ollama-nav.pngimages2001.00 s4.7 KB
https://ollama.com/public/apple-touch-icon.pngimages200995 ms5.4 KB
https://ollama.com/public/icon-64x64.pngimages200995 ms1.8 KB
https://ollama.com/public/icon-48x48.pngimages200993 ms1.3 KB
https://ollama.com/public/icon-16x16.pngimages200989 ms458 B
https://ollama.com/public/vendor/htmx/bundle.jsjavascript200987 ms87.6 KB
https://ollama.com/public/logos/mercedes.svgimages200986 ms439 B
https://ollama.com/public/logos/apple.svgimages200985 ms656 B
https://ollama.com/public/logos/nike.svgimages200984 ms400 B
https://ollama.com/public/android-chrome-icon-512x512.pnghtml404979 ms11.9 KB
https://ollama.com/public/logos/intel.svgimages200979 ms1.8 KB
https://ollama.com/public/android-chrome-icon-192x192.pnghtml404977 ms11.9 KB
https://ollama.com/public/logos/meta.svgimages200977 ms1.3 KB
https://ollama.com/public/icon-32x32.pngimages200972 ms890 B
https://ollama.com/public/logos/ibm.svgimages200965 ms1.8 KB
https://ollama.com/public/logos/visa.svgimages200965 ms798 B
https://ollama.com/public/logos/netflix.svgimages200963 ms280 B
https://ollama.com/public/logos/nasa.svgimages200962 ms1.4 KB
https://ollama.com/public/logos/adobe.svgimages200960 ms222 B
https://ollama.com/public/logos/microsoft.svgimages200956 ms3.0 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.