stitchfulnotes.com website review

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

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

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

About 91 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

43 KiB could be saved by minifying JavaScript.

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

7 third-party services load with your homepage (sealsubscriptions.com, Klaviyo and shrinetheme.com and others), adding 353 KiB and 90 ms of main-thread time.

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

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

3 KiB could be saved by minifying CSS.

Your largest element takes 19.6 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.6 s. Good is under 3.8 s.

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

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

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 4.1 MB in 160 requests on a phone: images 2.7 MB (6), other files 820 KiB (93) and scripts 432 KiB (52). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

<td> elements in a large <table> do not have table headers. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 17 characters: “Origami Art Class”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “Origami Master Guide [Free Today]”). 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 23 pages on stitchfulnotes.com and 3 external pages.

https://origami-class.com/products/1000-origami-notes, https://origami-class.com/pages/portal-page, https://origami-class.com/pages/contact, https://origami-class.com/collections/all, https://origami-class.com/policies/contact-information and https://origami-class.com/policies/shipping-policy and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://origami-class.com/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

https://origami-class.com/pages/contact and https://origami-class.com/policies/contact-information have 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 12 pages linked from your homepage 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 429 ()”.

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

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

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.

The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

The page uses urgency cues (a countdown or limited-time wording).

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