willowwinterswrites.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Clarity and minmaxify.com and others), adding 1.6 MB and 973 ms of main-thread time.

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

Shopify costs a phone 563 ms of main-thread work and 1.0 MB 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 318 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

smile.io costs a phone 79 ms of main-thread work and 357 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.

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

75 KiB could be saved by minifying JavaScript.

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

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

2 KiB could be saved by minifying CSS.

Polyfills for old browsers add 7 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.

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

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dark moody photograph of bare tree branches silhouetted aga…”.

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

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

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

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

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

Your homepage downloads 6.9 MB in 319 requests on a phone: images 4.0 MB (55), scripts 1.2 MB (136) and other files 1.0 MB (92). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example Willow_Logo_2x_b5e6a58b-676e-46aa-adf1-14125fffb2c3.png at 4,452 px wide, shown at 65 px. Resized copies would save about 504 KiB.

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

By the Sustainable Web Design model, a visit to your homepage emits about 1.94 g of CO₂e: 233.4 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.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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.

There are 2 <h1> headlines (“Signed in Blood Is Out Now” and “Not Sure What to Read Next?”). One clear main headline is easier for people and search engines.

The homepage links to 140 pages on willowwinterswrites.com and 22 external pages.

https://willowwinterswrites.com/discount/NEW30 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://willowwinterswrites.com/discount/NEW30 all use the title “Willow Winters Publishing LLC – Willow Winters® Publishing LLC”. Search engines can't tell which page to show for a search, so each competes with the others.

https://willowwinterswrites.com/collections/all, https://willowwinterswrites.com/collections/all-books, https://willowwinterswrites.com/pages/ready-to-ship-mystery-boxes, https://willowwinterswrites.com/collections/special-editions, https://willowwinterswrites.com/pages/newreleases and https://willowwinterswrites.com/collections/discreet-series and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://willowwinterswrites.com/collections/huge-savings, https://willowwinterswrites.com/collections/all, https://willowwinterswrites.com/collections/all-books, https://willowwinterswrites.com/pages/ready-to-ship-mystery-boxes, https://willowwinterswrites.com/collections/special-editions and https://willowwinterswrites.com/pages/newreleases and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://willowwinterswrites.com/discount/NEW30, https://willowwinterswrites.com/collections/all, https://willowwinterswrites.com/collections/all-books, https://willowwinterswrites.com/pages/sortbytropes, https://willowwinterswrites.com/collections/merchandise and https://willowwinterswrites.com/collections/damaged-books-1 and 1 other took over 3 s to send their HTML from our server.

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

23 of 47 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://demandforapps.com/external-links/css/add_ext_link.css' from origin 'https://willow…”.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

Before a visitor clicks anything, the page loads Meta Pixel, Microsoft Clarity and Pinterest Tag (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 17 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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.