Website review, no card needed

fabledots.com logo

fabledots.com website review

Visit site (opens in a new tab)Reviewed 16 November 202638 issues · 79 checks

This review found 38 issues worth fixing on fabledots.com, 14 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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

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

How it loaded on a phone

  1. fabledots.com at 0.8 s0.8 s
  2. fabledots.com at 1.6 s1.6 s
  3. fabledots.com at 2.3 s2.3 s
  4. fabledots.com at 3.1 s3.1 s
  5. fabledots.com at 3.9 s3.9 s
  6. fabledots.com at 4.7 s4.7 s
  7. fabledots.com at 5.5 s5.5 s
  8. fabledots.com at 6.2 s6.2 s

Speed

11 to fix53
  • Reduce unused JavaScript

    3.8 s · 767 KiB

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

  • Main-thread work: 4.0 s

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

  • 3,301 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Shopify and Hotjar and others), adding 2.1 MB and 1.3 s of main-thread time.

  • Mobile performance score: 53

    53/100

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

  • Reduce unused CSS

    450 ms · 146 KiB

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

  • YouTube adds 480 ms

    480 ms

    YouTube costs a phone 480 ms of main-thread work and 999 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 adds 407 ms

    407 ms

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

  • Render-blocking requests

    450 ms

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

  • Hotjar adds 348 ms

    348 ms

    Hotjar costs a phone 348 ms of main-thread work and 67 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.

  • 10 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 ms · 49 KiB

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

  • Improve image delivery

    50 ms · 56 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • 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: 16 ms

    16 ms

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

Core Web Vitals

5 to fix64
  • First Contentful Paint: 12.5 s

    12.5 s

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

  • Largest Contentful Paint: 32.1 s

    32.1 s

    Your largest element takes 32.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CUSTOM KEYCHAINS”.

  • Time to Interactive: 32.2 s

    32.2 s

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

  • Speed Index: 13.5 s

    13.5 s

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

  • 15 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 173 ms

    173 ms

    Scripts block the page for only 173 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix69
  • Page weight: 6.8 MB in 470 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 470 requests on a phone: scripts 3.7 MB (193), other files 1.2 MB (189) and stylesheets 923 KiB (54). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • 1 image below the first screen load straight away

    1 image further down the page (28 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.93 g

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

6 to fixGoogle 9492
  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (1 element)

    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 (5 elements)

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

  • 2 form fields without a label

    2 form fields have 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.

2 checks passed
  • Every image has alt text

    All 43 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9275
  • No meta description

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

  • Title is short (9 characters)

    Your title is only 9 characters: “FableDots”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 92 internal links, 7 external

    The homepage links to 92 pages on fabledots.com and 7 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

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

  • XML sitemap found

    Your XML sitemap is reachable at https://fabledots.com/sitemap.xml.

AI search readiness

100
4 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,527 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://fabledots.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix60
  • 1 page without a title

    https://fabledots.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://fabledots.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://fabledots.com/a/faq all use the title “FableDots”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://fabledots.com/collections/all, https://fabledots.com/collections/creative-acrylic, https://fabledots.com/a/faq and https://fabledots.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://fabledots.com/collections/all, https://fabledots.com/collections/new-arrivals, https://fabledots.com/collections/custom-keychains, https://fabledots.com/collections/custom-standees, https://fabledots.com/collections/fridge-magnets and https://fabledots.com/collections/creative-acrylic and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://fabledots.com/collections/creative-acrylic has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

Best practices

3 to fixGoogle 7376
  • 2 broken images

    2 images failed to load on a phone, for example https://fabledots.com/.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    13 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

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

  • Phone number is not tap-to-call

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

  • 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 646 words of copy

    The homepage carries about 646 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Quote (0)”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”, “Get a Custom Quote” and “Contact Us”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Hotjar.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 1 more (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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 of them by other companies (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.

  • 36 other companies contacted

    Loading the homepage contacts 36 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 fabledots.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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Sa Request A Quote · Ymq Product Options · Judge Me Reviews · Klaviyo Email Marketing Sms · Ecomsend · getsitecontrol.com

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

Framework
jQuery
E-commerce
Shopify
Analytics
Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on fabledots.com, including 16 speed issues, 4 SEO issues and 1 conversion gap. 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