Website review, no card needed

natsbooknook.com logo

natsbooknook.com website review

Visit site (opens in a new tab)Reviewed 16 November 202636 issues · 80 checks

This review found 36 issues worth fixing on natsbooknook.com, 10 of them high impact, across 80 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.1 s811 msMay 30Nov 14887 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.1 s
Jun 20, 20261.0 s
Jun 27, 2026982 ms
Jul 4, 2026954 ms
Jul 25, 20261.0 s
Aug 1, 2026989 ms
Aug 8, 2026942 ms
Aug 15, 2026848 ms
Aug 22, 2026855 ms
Aug 29, 2026883 ms
Sep 5, 2026921 ms
Sep 12, 2026965 ms
Sep 19, 2026985 ms
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Nov 7, 2026998 ms
Nov 14, 2026887 ms
Real-visitor tap response (INP)75th percentile, phones
116 ms90 msJul 25Nov 14104 ms
Show as table
DateReal-visitor tap response (INP)
Jul 25, 2026104 ms
Aug 1, 2026102 ms
Aug 8, 202693 ms
Aug 29, 2026102 ms
Sep 5, 2026104 ms
Sep 12, 2026103 ms
Sep 19, 2026104 ms
Oct 31, 2026113 ms
Nov 7, 2026112 ms
Nov 14, 2026104 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of natsbooknook.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. natsbooknook.com at 0.4 s0.4 s
  2. natsbooknook.com at 0.8 s0.8 s
  3. natsbooknook.com at 1.2 s1.2 s
  4. natsbooknook.com at 1.6 s1.6 s
  5. natsbooknook.com at 2.0 s2.0 s
  6. natsbooknook.com at 2.4 s2.4 s
  7. natsbooknook.com at 2.8 s2.8 s
  8. natsbooknook.com at 3.1 s3.1 s

Speed

10 to fix59
  • Improve image delivery

    1.1 s · 872 KiB

    12 images could be 872 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • 3,580 HTML elements

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

  • Mobile performance score: 59

    59/100

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

  • Reduce unused JavaScript

    750 ms · 126 KiB

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

  • Use efficient cache lifetimes

    650 ms · 135 KiB

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

  • 8 third-party services on the page

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

  • Font display

    550 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).

  • Main-thread work: 3.0 s

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

  • Shopify adds 200 ms

    200 ms

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

  • flodesk.com adds 69 ms

    69 ms

    flodesk.com costs a phone 69 ms of main-thread work and 1.1 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.

  • Legacy JavaScript

    200 ms · 35 KiB

    Polyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 4 long tasks on the main thread

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

  • Duplicated JavaScript

    150 ms · 26 KiB

    26 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    100 ms

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

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 12 ms

    12 ms

    Your server sent the HTML in 12 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 17.9 s

    17.9 s

    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.

  • Time to Interactive: 18.4 s

    18.4 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Total Blocking Time: 216 ms

    216 ms

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

  • Tap response (INP) held steady for real visitors

    +5%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix64
  • Page weight: 4.4 MB in 246 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 246 requests on a phone: images 2.2 MB (19), other files 945 KiB (102) and scripts 786 KiB (89). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    IMG_0467__1.jpg 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).

  • About 1.2 g of CO₂ per visit

    1.24 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9795
  • 54 text elements with low contrast

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

  • All page content should be contained by landmarks (12 elements)

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

  • 1 form field without a label

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

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

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

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9272
  • No meta description

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

  • Title is short (23 characters)

    Your title is only 23 characters: “Nat's Book Nook Pty Ltd”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

    No XML sitemap at https://natsbooknook.com/sitemap.xml, so Google discovers your pages only by following links.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • One H1 headline

    Your <h1> is empty.

  • 143 internal links, 13 external

    The homepage links to 143 pages on natsbooknook.com and 13 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://natsbooknook.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

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

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,727 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 4 pages without a meta description

    https://natsbooknook.com/pages/nats-noticeboard, https://natsbooknook.com/collections/caraval-once-upon-a-broken-heart-p1-collection, https://natsbooknook.com/collections/all and https://natsbooknook.com/collections have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://natsbooknook.com/pages/nats-noticeboard has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7387
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 4 JavaScript errors while loading

    4 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 HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

2 checks passed
  • Tap targets are thumb-sized

    26 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

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

  • Thin social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

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

  • About 587 words of copy

    The homepage carries about 587 words of visible text.

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “SHOP ALL”, “SHOP ALL COLLECTIONS” and “SHOP ALL PRODUCTS”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 25 other companies contacted

    Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at natsbooknook.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Sk Contact Form Builder · Judge Me Reviews · Cbb Shipping Rates · Sami Wholesale · Minmaxify Order Limits · Nova Multi Currency Converter

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on natsbooknook.com, including 15 speed issues, 5 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25