Website review, no card needed

n2o.co.uk logo

n2o.co.uk website review

Visit site (opens in a new tab)Reviewed 18 November 202638 issues · 87 checks

This review found 38 issues worth fixing on n2o.co.uk, 9 of them high impact, across 87 checks. The most urgent: render-blocking requests. 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.7 s983 msMay 30Nov 141.5 s
Show as table
DateReal-visitor load time (LCP)
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.3 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.2 s
Sep 12, 20261.3 s
Sep 19, 20261.5 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.4 s
Oct 24, 20261.3 s
Oct 31, 20261.4 s
Nov 7, 20261.3 s
Nov 14, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
117 ms83 msMay 30Nov 14109 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202697 ms
Jun 6, 202699 ms
Jun 13, 2026103 ms
Jun 20, 2026102 ms
Jun 27, 2026101 ms
Jul 4, 202698 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202687 ms
Aug 15, 202687 ms
Aug 22, 202692 ms
Aug 29, 202690 ms
Sep 5, 202697 ms
Sep 12, 2026102 ms
Sep 19, 202692 ms
Sep 26, 202696 ms
Oct 3, 2026100 ms
Oct 10, 2026100 ms
Oct 17, 2026113 ms
Oct 24, 2026107 ms
Oct 31, 2026110 ms
Nov 7, 2026109 ms
Nov 14, 2026109 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 n2o.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. n2o.co.uk at 0.4 s0.4 s
  2. n2o.co.uk at 0.8 s0.8 s
  3. n2o.co.uk at 1.1 s1.1 s
  4. n2o.co.uk at 1.5 s1.5 s
  5. n2o.co.uk at 1.9 s1.9 s
  6. n2o.co.uk at 2.3 s2.3 s
  7. n2o.co.uk at 2.6 s2.6 s
  8. n2o.co.uk at 3.0 s3.0 s

Speed

12 to fix57
  • Render-blocking requests

    4.0 s

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.

  • 8 third-party services on the page

    8 third-party services load with your homepage (website-files.com, Vimeo and Google Tag Manager and others), adding 24.8 MB and 1.1 s of main-thread time.

  • Vimeo adds 323 ms

    323 ms

    Vimeo costs a phone 323 ms of main-thread work and 22.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.

  • Reduce unused JavaScript

    750 ms · 1.2 MB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

  • website-files.com adds 501 ms

    501 ms

    website-files.com costs a phone 501 ms of main-thread work and 1.9 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.

  • Use efficient cache lifetimes

    300 ms · 162 KiB

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

  • Improve image delivery

    460 KiB

    4 images could be 460 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Main-thread work: 4.0 s

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

  • Reduce unused CSS

    258 KiB

    About 258 KiB of CSS is downloaded but never applied on this page.

  • 2,360 HTML elements

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

  • Google Tag Manager adds 176 ms

    176 ms

    Google Tag Manager costs a phone 176 ms of main-thread work and 328 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.

  • 14 long tasks on the main thread

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Minify CSS

    50 KiB

    50 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    17 KiB

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

  • Chained critical requests

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

  • 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: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 24.0 s

    24.0 s

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

  • Speed Index: 10.6 s

    10.6 s

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

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • Largest Contentful Paint: 4.3 s

    4.3 s

    Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are N2O”.

  • Largest content (LCP) got 20% slower for real visitors

    +20%

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

  • Total Blocking Time: 447 ms

    447 ms

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

  • Tap response (INP) got 11% slower for real visitors

    +11%

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

7 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.9 s

    1.9 s

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

  • Real-user INP: 120 ms

    120 ms

    Real visitors wait 120 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.6 s

    1.6 s

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

  • Real-user TTFB: 438 ms

    438 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 25.6 MB in 164 requests

    25.6 MB

    Your homepage downloads 25.6 MB in 164 requests on a phone: other files 21.2 MB (66), scripts 2.3 MB (42) and images 1.0 MB (27). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    69847b6efe97f02e08c339f8_N2O Award Winning Brand Experience is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images in older formats

    3 images (143 KiB) are 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.

  • About 7.3 g of CO₂ per visit

    7.27 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9093
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (56 elements)

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

  • 10 form fields without a label

    10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 136 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.

  • 3 links with vague text

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

  • 115 internal links, 17 external

    The homepage links to 115 pages on n2o.co.uk and 17 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Award-winning brand experience agency creating powerful experiential campaigns, retail activations, social campaigns & …”.

  • One H1 headline

    Your main headline reads: “Award-Winning Brand Experience Agency”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “N2O | Award-Winning Brand Experience Agency”.

  • Canonical URL set

    The canonical URL is https://www.n2o.co.uk/.

  • 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://www.n2o.co.uk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.n2o.co.uk/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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix81
  • 4 pages share a title

    https://www.n2o.co.uk/resources, https://www.n2o.co.uk/resources/n2o-insights-easter-brand-playbook, https://www.n2o.co.uk/resources/n2o-insights-generational-ai-attitudes-behaviours and https://www.n2o.co.uk/resources/n20-insights-no-low-alcohol-consumer-behaviour all use the title “Resources: White Papers, Reports & Insights | N2O”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.n2o.co.uk/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.n2o.co.uk/resources, https://www.n2o.co.uk/resources/n2o-insights-easter-brand-playbook, https://www.n2o.co.uk/resources/n2o-insights-generational-ai-attitudes-behaviours and https://www.n2o.co.uk/resources/n20-insights-no-low-alcohol-consumer-behaviour use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.n2o.co.uk/resources/n2o-insights-easter-brand-playbook, whose canonical is https://www.n2o.co.uk/resources. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5483
  • 4 small tap targets

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

  • 2 third-party cookies

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

  • Deprecated browser APIs

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “[marquee] Invalid height value for fs-marquee-instance="fs-marquee-4". If you are using Images ensure to set loading="e…”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 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 1,257 words of copy

    The homepage carries about 1,257 words of visible text.

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “/ Learn more about us” and “Book a call”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks, 40 customer or partner logos and 12 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 3 of them by other companies (measured from a US location before any click).

  • 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.

  • 28 other companies contacted

    Loading the homepage contacts 28 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 n2o.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Analytics | Google Tag Manager
Hosting
Webflow

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on n2o.co.uk, including 18 speed issues, 2 SEO issues and 2 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