Programmable

Website review, no card needed

sparkly-trees.com logo

sparkly-trees.com website review

Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 71 checks

This review found 32 issues worth fixing on sparkly-trees.com, 6 of them high impact, across 71 checks. The most urgent: render-blocking requests. 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

Site score

85B

Closest competitors among WooCommerce stores

Compare side by side

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

sparkly-trees.com (opens in a new tab)
Full-page screenshot of sparkly-trees.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sparkly-trees.com at 0.6 s0.6 s
  2. sparkly-trees.com at 1.2 s1.2 s
  3. sparkly-trees.com at 1.8 s1.8 s
  4. sparkly-trees.com at 2.4 s2.4 s
  5. sparkly-trees.com at 3.0 s3.0 s
  6. sparkly-trees.com at 3.6 s3.6 s
  7. sparkly-trees.com at 4.1 s4.1 s
  8. sparkly-trees.com at 4.7 s4.7 s

Speed

3 to fix91

  • Render-blocking requests

    1.0 s

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

  • Improve image delivery

    2.3 MB

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

  • Use efficient cache lifetimes

    369 KiB

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

  • 3 long tasks on the main thread

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

  • Reduce unused JavaScript

    10 ms · 21 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and hostinger.com), adding 89 KiB and 6 ms of main-thread time.

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

3 checks passed

  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 377 ms of it running JavaScript. That is comfortably low.

  • Server response: 55 ms

    55 ms

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

Core Web Vitals

4 to fix97

  • Speed Index: 5.2 s

    5.2 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Time to Interactive: 5.3 s

    5.3 s

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

  • 10 images without width and height

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

3 checks passed

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Turn ordinary evenings into 'wow, is this really my room?' …”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 20 ms

    20 ms

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

Images and page weight

4 to fix48

  • 10 images far larger than shown

    1.9 MB

    10 images are downloaded at several times the size a phone draws them, for example WhatsApp-Image-2025-12-12-at-6.41.13-AM-1.jpeg at 1,600 px wide, shown at 154 px. Resized copies would save about 1.9 MB.

  • Page weight: 3.5 MB in 106 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 106 requests on a phone: images 3.1 MB (40), scripts 200 KiB (30) and fonts 76 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 12 images in older formats

    12 images (2.4 MB) are 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.

  • 6 images below the first screen load straight away

    6 images further down the page (343 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.98 g

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

Accessibility

7 to fixGoogle 9092

  • 15 text elements with low contrast

    15 text elements don'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 (37 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed

  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 9276

  • No meta description

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

  • Title is short (13 characters)

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 71 internal links, 0 external

    The homepage links to 71 pages on sparkly-trees.com and 0 external pages.

4 checks passed

  • One H1 headline

    Your main headline reads: “Fill Your Home With Magic”.

  • Canonical URL set

    The canonical URL is https://sparkly-trees.com/.

  • 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://sparkly-trees.com/wp-sitemap.xml.

AI search readiness

1 to fix88

  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://sparkly-trees.com/llms.txt (48 KiB, 99 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix78

  • 2 pages share a title

    https://sparkly-trees.com/products/light-reflection-rings and https://sparkly-trees.com/product/light-reflection-rings all use the title “I ❤️ You – Light Reflection Rings – Sparkly Trees”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://sparkly-trees.com/product-category/valentines-day, https://sparkly-trees.com/product/the-rose-flower-tree-lights-sparkly-trees, https://sparkly-trees.com/product-category/sparkly-trees-magical-treasury, https://sparkly-trees.com/product-category/led-incense-burners, https://sparkly-trees.com/reviews and https://sparkly-trees.com/contact-us and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://sparkly-trees.com/products/light-reflection-rings, whose canonical is https://sparkly-trees.com/product/light-reflection-rings. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://sparkly-trees.com/elementor-12241 has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://sparkly-trees.com/reviews and https://sparkly-trees.com/elementor-12241 have 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 28 found) and read each the way a search engine does.

3 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087

  • 8 small tap targets

    8 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • About 791 words of copy

    The homepage carries about 791 words of visible text.

4 checks passed

  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact Us” and “Shop Now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 36 testimonial or review blocks, 4 customer or partner logos, a star rating, 6 trust badges and “303,050 + Happy Customers”.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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.

  • 4 other companies contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 sparkly-trees.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on sparkly-trees.com, including 7 speed issues, 4 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