kickprocrastination.com website review

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

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

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

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

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

rebuyengine.com costs a phone 177 ms of main-thread work and 300 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.

Klaviyo costs a phone 166 ms of main-thread work and 309 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.

8 third-party services load with your homepage (rebuyengine.com, Klaviyo and sealsubscriptions.com and others), adding 933 KiB and 422 ms of main-thread time.

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

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

43 KiB could be saved by minifying JavaScript.

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

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

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

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.

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

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

Real visitors wait 207 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors wait 838 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

3 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' largest content (lcp) went from 2.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

crochet_gif04-ezgif.com-video-to-gif-converter_1.gif weighs 2.6 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.7 MB in 214 requests on a phone: images 1.7 MB (12), scripts 906 KiB (71) and other files 856 KiB (114). Under 2 MB keeps phones on slow connections fast.

1 image (2.6 MB) 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.

ChatGPT_Image_23_._2026_._16_56_59.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).

1 image further down the page (30 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 1.04 g of CO₂e: 125.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Table header text 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 13 characters: “Crochet Notes”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “1.000+ Free Crochet Notes”). 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.

The homepage links to 24 pages on kickprocrastination.com and 3 external pages.

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

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

We fetched 12 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 133 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).

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