Website review, no card needed

layerzero.network logo

layerzero.network website review

Visit site (opens in a new tab)Reviewed 18 October 202620 issues · 71 checks

This review found 20 issues worth fixing on layerzero.network, 6 of them high impact, across 71 checks. The most urgent: main-thread work: 5.7 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.5 s1.2 sApr 25Oct 101.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.4 s
May 2, 20261.4 s
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.5 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
148 ms103 msApr 25Oct 10108 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026143 ms
May 2, 2026135 ms
May 9, 2026132 ms
May 16, 2026128 ms
May 23, 2026126 ms
May 30, 2026125 ms
Jun 6, 2026118 ms
Jun 13, 2026119 ms
Jun 20, 2026120 ms
Jun 27, 2026113 ms
Jul 4, 2026113 ms
Jul 11, 2026111 ms
Jul 18, 2026111 ms
Jul 25, 2026114 ms
Aug 1, 2026115 ms
Aug 8, 2026117 ms
Aug 15, 2026114 ms
Aug 22, 2026114 ms
Aug 29, 2026109 ms
Sep 5, 2026110 ms
Sep 12, 2026113 ms
Sep 19, 2026108 ms
Sep 26, 2026112 ms
Oct 3, 2026108 ms
Oct 10, 2026108 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of layerzero.network (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. layerzero.network at 0.7 s0.7 s
  2. layerzero.network at 1.3 s1.3 s
  3. layerzero.network at 2.0 s2.0 s
  4. layerzero.network at 2.6 s2.6 s
  5. layerzero.network at 3.3 s3.3 s
  6. layerzero.network at 3.9 s3.9 s
  7. layerzero.network at 4.6 s4.6 s
  8. layerzero.network at 5.2 s5.2 s

Speed

5 to fix72
  • Main-thread work: 5.7 s

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

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72 (desktop: 98). Pages that score under 90 lose visitors before the first paint.

  • 13 long tasks on the main thread

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

  • Hubspot adds 283 ms

    283 ms

    Hubspot costs a phone 283 ms of main-thread work and 103 KiB 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.

  • 1,531 HTML elements

    The page has 1,531 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Hubspot and Google Fonts), adding 142 KiB and 283 ms of main-thread time.

  • Use efficient cache lifetimes

    94 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (94 KiB).

  • Reduce unused JavaScript

    79 KiB

    About 79 KiB of JavaScript is downloaded but never used on this page.

  • Legacy JavaScript

    27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 72. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Forced reflow

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

1 checks passed
  • Server response: 28 ms

    28 ms

    Your server sent the HTML in 28 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Time to Interactive: 7.3 s

    7.3 s

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

  • Speed Index: 5.4 s

    5.4 s

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 109 ms

    109 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 700 ms

    700 ms

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

  • Tap response (INP) got 22% faster for real visitors

    -22%

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

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Powering the global movement and exchange of value.”.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.17 g

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

4 checks passed
  • Page weight: 605 KiB in 40 requests

    605 KiB

    Your homepage downloads 605 KiB in 40 requests on a phone: scripts 407 KiB (21), fonts 108 KiB (3) and HTML 56 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 9698
  • 18 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • Title is short (9 characters)

    Your title is only 9 characters: “LayerZero”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (48 characters)

    Your meta description is only 48 characters: “Permissionless Infrastructure for a Better World”. 70 to 160 characters is enough to sell the click.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 88 internal links, 13 external

    The homepage links to 88 pages on layerzero.network and 13 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Powering the global movement and exchange of value.”.

  • Canonical URL set

    The canonical URL is https://layerzero.network/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://layerzero.network/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://layerzero.network/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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,929 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://layerzero.network/interop has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://layerzero.network/careers has 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.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 9 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    14 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix20
  • No call to action on the first screen

    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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

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

  • About 261 words of copy

    The homepage carries about 261 words of visible text.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads HubSpot (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.

  • No consent tool detected

    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.

  • 8 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at layerzero.network, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Vercel

Hiring

Hiring
7 open roles
Teams
Engineering (5), Business Development (1), Finance (1)
Job board
greenhouse

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on layerzero.network, including 8 speed issues, 3 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25