petiteknit.com website review

The page goes through 1 redirect before it starts loading, costing about 9.0 s. Link and advertise the final URL directly.

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

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

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

8 third-party services load with your homepage (shgcdn2.com, Shopify and Klaviyo and others), adding 609 KiB and 1.5 s of main-thread time.

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

shgcdn2.com costs a phone 497 ms of main-thread work and 68 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.

Shopify costs a phone 340 ms of main-thread work and 308 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 324 ms. During a long task the page ignores taps.

12 KiB could be saved by minifying JavaScript.

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

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

About 11 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.

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

Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Kinde iført bordeaux og blåt Yoko Set”.

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

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

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

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

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

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

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

Your homepage downloads 5.5 MB in 407 requests on a phone: images 2.6 MB (54), other files 1.4 MB (222) and scripts 1.1 MB (105). Under 2 MB keeps phones on slow connections fast.

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

7 images have 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.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails 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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 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 10 characters: “PetiteKnit”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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

The homepage links to 138 pages on petiteknit.com and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.petiteknit.com/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.

Your homepage links to https://www.petiteknit.com/collections/huer, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.petiteknit.com/collections/digitale-opskrifter has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.petiteknit.com/collections/digitale-opskrifter has no <h1> headline, so visitors and search engines get no clear main topic.

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

7 images failed to load on a phone, for example https://views.unsplash.com/v?app_id=226925&photo_id=gid://shopify/ImageSource/72233143173456.

4 of 18 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 “Access to XMLHttpRequest at 'https://a.shgcdn2.com/css-2026-03-06-0655/6ad8b7d99ba4e2a5d0dc4526_6ad8b7da9ba4e2a5d0dc47a…”.

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 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 109 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Klaviyo (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 6 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.