blavity.com website review

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

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

7 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Wunderkind and Pubmatic and others), adding 2.5 MB and 1.5 s of main-thread time.

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

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

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

Google/Doubleclick Ads costs a phone 189 ms of main-thread work and 450 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.

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

Taboola costs a phone 161 ms of main-thread work and 411 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 162 ms. During a long task the page ignores taps.

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

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

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

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.

Your largest element takes 38.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “If you wish to opt-out of the sale, sharing to third partie…”.

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

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

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

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

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

The layout shifts by 0.105 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 7.2 MB in 650 requests on a phone: scripts 4.6 MB (152), images 1.9 MB (131) and other files 501 KiB (299). Under 2 MB keeps phones on slow connections fast.

roberto-sorin-RS0-h_pyByk-unsplash-scaled.jpg weighs 810 KiB. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example roberto-sorin-RS0-h_pyByk-unsplash-scaled.jpg at 2,560 px wide, shown at 326 px. Resized copies would save about 1.2 MB.

5 images further down the page (1.5 MB) 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 2.05 g of CO₂e: 245.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

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

Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

[role]s are not contained by their required parent element (1 element).

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

Some lists contain elements other than list items, which screen readers announce wrongly.

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 73 pages on blavity.com and 24 external pages.

https://blavity.com/briefing has no <title>, so Google invents the link text in results.

https://blavity.com/briefing and https://blavity.com/categories/culture use the same meta description. A description written for each page earns more clicks.

https://blavity.com/briefing 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.

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

1 image failed to load on a phone, for example https://ams-pageview-public.s3.amazonaws.com/1x1-pixel.png?id=98e744abd983.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Attribution Reporting is deprecated and will be removed. See https://goo.gle/ps-status for details.”).

5 errors were logged to the browser console while the page loaded, for example “Hydration completed but contains mismatches.”.

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

Requests the notification permission on page load.

Large scripts ship without source maps.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 713 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 6 mores (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 27 cookies, 1 of them by other companies (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 66 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.