300magazine.com website review

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

About 1.2 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 7.2 s faster on a phone.

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

About 739 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.

2 images could be 302 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

135 KiB could be saved by minifying JavaScript.

76 KiB could be saved by minifying CSS.

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

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

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

4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and JSDelivr CDN and others), adding 941 KiB and 330 ms of main-thread time.

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

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.

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

Your largest element takes 29.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Yoshitomo Nara: Beyond the Cute”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 9.9 MB in 84 requests on a phone: images 6.3 MB (11), scripts 1.5 MB (30) and stylesheets 1.3 MB (27). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example YNARADZ20SHOW2026_FLOOR1_INSTALL_V17-scaled.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 243 KiB.

2 images (314 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.

1 image further down the page (122 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (12 elements).

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 109 pages on 300magazine.com and 3 external pages.

https://300magazine.com/art-deus-and-machina, https://300magazine.com/evija-freidenfelde-where-memory-becomes-matter, https://300magazine.com/tag/exhibitions, https://300magazine.com/tag/venice-biennale, https://300magazine.com/tag/biennales and https://300magazine.com/tag/perspectives and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://300magazine.com/tag/exhibitions, https://300magazine.com/tag/venice-biennale, https://300magazine.com/tag/biennales, https://300magazine.com/tag/perspectives, https://300magazine.com/tag/conceptual-art and https://300magazine.com/tag/curatorship have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://300magazine.com/.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener') https://300magazine.com/:416:17”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.