weareknitters.ca website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Facebook and others), adding 3.2 MB and 2.9 s of main-thread time.

34 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 120 ms faster on a phone.

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

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

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

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

Facebook costs a phone 303 ms of main-thread work and 283 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.

growave.io costs a phone 268 ms of main-thread work and 238 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 278 ms. During a long task the page ignores taps.

ZenDesk costs a phone 206 ms of main-thread work and 386 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 37 KiB JavaScript that modern phones do not need.

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

8 KiB JavaScript is shipped twice across bundles.

6 KiB could be saved by minifying JavaScript.

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.

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.

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

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

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

Real visitors wait 205 ms for the page to respond to a tap (75th percentile). 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.7 s on a phone. Good is under 1.8 s.

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

The layout shifts by 0.103 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' tap response (inp) went from 187 ms to 213 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.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 45.1 MB in 450 requests on a phone: media 35.5 MB (7), images 4.9 MB (81) and scripts 3.3 MB (149). Under 2 MB keeps phones on slow connections fast.

Knitmas_Mobile_Qualidade_Melhorada.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images are downloaded at several times the size a phone draws them, for example Knitmas_Mobile_Qualidade_Melhorada.png at 1,500 px wide, shown at 390 px. Resized copies would save about 167 KiB.

1 image (123 KiB) is 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.

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 10 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.

2 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.

ARIA role should be appropriate for the element: 4 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.

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

Your title is 88 characters, so Google will cut it off around 60: “We Are Knitters: craft your joy with yarn and easy and advanced patter – We Are Knitters”.

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

Your meta description is 192 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 346 pages on weareknitters.ca and 13 external pages.

There is no https://weareknitters.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.

https://weareknitters.com/collections/yarn and https://weareknitters.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://weareknitters.com/products/10-pack-of-dancing-queen-yarn-balls and https://weareknitters.com/collections/kits have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 1,346 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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 26 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 58 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.