tezos.com website review

46 files are served with short cache lifetimes, so returning visitors download them again (3.3 MB).

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.6 s faster on a phone.

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

7 third-party services load with your homepage (Google Tag Manager, Vimeo and posthog.com and others), adding 7.6 MB and 340 ms of main-thread time.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Vimeo costs a phone 158 ms of main-thread work and 7.4 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Polyfills for old browsers add 79 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

About 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

A phone's processor spends 3.3 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

10 long tasks block the main thread while loading, the longest for 275 ms. During a long task the page ignores taps.

4 images could be 107 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

The first text or image appears after 16.5 s on a phone. Good is under 1.8 s.

Your largest element takes 33.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to the next generation in blockchain design: modula…”.

Visually, the page fills in at 16.5 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 36.8 s. Good is under 3.8 s.

Real visitors wait 229 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

Real visitors wait 947 ms for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 591 ms in total while the page loads. Good is under 200 ms.

2 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 181 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.1 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.2 MB in 86 requests on a phone: other files 7.6 MB (33), scripts 3.0 MB (25) and HTML 1.6 MB (2). Under 2 MB keeps phones on slow connections fast.

1 image (91 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

2 images further down the page (112 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 3.74 g of CO₂e: 449.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

4 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 65 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

10 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 12 characters: “Home | Tezos”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://tezos.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at tezos.com/robots.txt, the first file search crawlers ask for.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Open Graph is missing og:title, so shared links fall back to guesses.

The homepage links to 25 pages on tezos.com and 36 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://tezos.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://tezos.com/learn/activate has no <title>, so Google invents the link text in results.

https://tezos.com/tez declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://tezos.com/tez all use the title “Home | Tezos”. Search engines can't tell which page to show for a search, so each competes with the others.

https://tezos.com/ecosystem, https://tezos.com/defi and https://tezos.com/learn/activate have no meta description, so Google writes the search snippet from whatever text it finds.

https://tezos.com/community and https://tezos.com/tez use the same meta description. A description written for each page earns more clicks.

https://tezos.com/tezos-x, https://tezos.com/tezlink, https://tezos.com/tez, https://tezos.com/learn/activate, https://tezos.com/carbon and https://tezos.com/privacy-notice have no <h1> headline, so visitors and search engines get no clear main topic.

https://tezos.com/learn/activate and https://tezos.com/feedback have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Unrecognized Content-Security-Policy directive 'prefetch-src'.”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 895 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 4 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.