atticuspoetry.com website review

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

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

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

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

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

8 third-party services load with your homepage (route.com, Shopify and Accessibe Accessibility Overlay and others), adding 1.4 MB and 609 ms of main-thread time.

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

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

route.com costs a phone 279 ms of main-thread work and 542 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.

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

Shopify costs a phone 135 ms of main-thread work and 531 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.

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

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

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.

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

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 342 requests on a phone: images 1.8 MB (26), scripts 1.6 MB (156) and other files 1.1 MB (141). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (325 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example about.jpg at 389 px wide, shown at 129 px. Resized copies would save about 4 KiB.

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

8 elements hidden from screen readers can still receive keyboard focus.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 29 characters: “Atticus Poetry Official Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Atticus Poetry Official Store” and “”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 93 pages on atticuspoetry.com and 15 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://atticuspoetry.com/pages/books and https://atticuspoetry.com/collections/books all use the title “Books – Atticus Poetry Official Store”. Search engines can't tell which page to show for a search, so each competes with the others.

https://atticuspoetry.com/pages/books, https://atticuspoetry.com/pages/about, https://atticuspoetry.com/collections/atticus-favorites, https://atticuspoetry.com/collections/apparel, https://atticuspoetry.com/collections/hats and https://atticuspoetry.com/collections/tees and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://atticuspoetry.com/pages/books, https://atticuspoetry.com/pages/about, https://atticuspoetry.com/collections/atticus-favorites, https://atticuspoetry.com/collections/apparel, https://atticuspoetry.com/collections/hats and https://atticuspoetry.com/collections/tees and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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