twentythree.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.1 MB and 1.0 s of main-thread time.

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

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

Google CDN costs a phone 363 ms of main-thread work and 1.1 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.

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

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

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

6 KiB could be saved by minifying CSS.

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

4 KiB could be saved by minifying JavaScript.

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 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 24.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Plays Analytics”.

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

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

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

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

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

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

Your homepage downloads 39.4 MB in 354 requests on a phone: media 29.5 MB (11), scripts 5.8 MB (68) and images 2.4 MB (136). Under 2 MB keeps phones on slow connections fast.

Plays-Analytics.webp 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).

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

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

2 links inside paragraphs rely on colour alone to stand out.

All page content should be contained by landmarks: 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.

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

2 links have no real href, so search engines can't follow them.

The homepage links to 135 pages on twentythree.com and 19 external pages.

There is no /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.

/ and /video-marketing-platform all use the title “Video Marketing Platform | TwentyThree”. Search engines can't tell which page to show for a search, so each competes with the others.

/customers, /pricing, /reports and /help use the same meta description. A description written for each page earns more clicks.

/set-up-trial 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.

/video-marketing-platform took over 3 s to send its HTML from our server.

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

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

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

Large scripts ship without source maps.

Your certificate from Certainly · Certainly Intermediate R1 expires in 13 days. If it doesn't renew automatically, visitors get a security warning.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

twentythree.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: “500+ companies”. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,095 words of visible text.

DMARC is set to p=none, so mail pretending to be twentythree.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (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 3 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.