Website review, no card needed

violetflamechocolate.com logo

violetflamechocolate.com website review

Visit site (opens in a new tab)Reviewed 12 November 202629 issues · 81 checks

This review found 29 issues worth fixing on violetflamechocolate.com, 6 of them high impact, across 81 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

Real-visitor load time (LCP)75th percentile, phones
2.0 s866 msMay 23Nov 71.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.8 s
Jun 6, 20261.9 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.5 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Nov 7, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
181 ms97 msMay 23Nov 7107 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026144 ms
May 30, 2026140 ms
Jun 6, 2026153 ms
Jun 13, 2026137 ms
Jun 20, 2026144 ms
Jun 27, 2026147 ms
Jul 4, 2026155 ms
Jul 11, 2026171 ms
Jul 18, 2026165 ms
Jul 25, 2026166 ms
Aug 1, 2026155 ms
Aug 8, 2026166 ms
Aug 15, 2026164 ms
Aug 22, 2026162 ms
Aug 29, 2026161 ms
Sep 5, 2026155 ms
Sep 12, 2026166 ms
Sep 19, 2026171 ms
Sep 26, 2026170 ms
Oct 3, 2026149 ms
Oct 10, 2026149 ms
Oct 17, 2026143 ms
Oct 24, 2026119 ms
Oct 31, 2026110 ms
Nov 7, 2026107 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 violetflamechocolate.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix65
  • Reduce unused JavaScript

    2.4 s · 560 KiB

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

  • Mobile performance score: 65

    65/100

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

  • Improve image delivery

    650 ms · 149 KiB

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

  • Render-blocking requests

    600 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, rechargecdn.com and Klaviyo and others), adding 1.4 MB and 296 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 91 KiB

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

  • Shopify adds 137 ms

    137 ms

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

  • 1,965 HTML elements

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

  • rechargecdn.com adds 60 ms

    60 ms

    rechargecdn.com costs a phone 60 ms of main-thread work and 296 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.

  • Use efficient cache lifetimes

    250 ms · 62 KiB

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

  • Legacy JavaScript

    150 ms · 19 KiB

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

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify JavaScript

    27 KiB

    27 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 13 ms

    13 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 18.3 s

    18.3 s

    Your largest element takes 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Violet Flame gift box on marble”.

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

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

    1.6 s

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

  • Real-user INP: 121 ms

    121 ms

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

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

  • Real-user TTFB: 282 ms

    282 ms

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

  • Tap response (INP) got 24% faster for real visitors

    -24%

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

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

    -43%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.0 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).

  • Total Blocking Time: 38 ms

    38 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 237 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 237 requests on a phone: scripts 1.4 MB (118), images 767 KiB (14) and other files 752 KiB (86). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (48 KiB) 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.

  • 2 images below the first screen load straight away

    2 images further down the page (74 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.96 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

4 to fixGoogle 8895
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (175 characters)

    Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 84 internal links, 6 external

    The homepage links to 84 pages on violetflamechocolate.com and 6 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Violet Flame Chocolate”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Violet Flame Chocolate by Katrina Markoff”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (1,047 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 5 pages without a meta description

    https://violetflamechocolate.com/collections/holiday-gift-guide, https://violetflamechocolate.com/collections/all, https://violetflamechocolate.com/collections/truffles, https://violetflamechocolate.com/collections/exquisite-gifts and https://violetflamechocolate.com/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://violetflamechocolate.com/collections/holiday-gift-guide, https://violetflamechocolate.com/collections/all, https://violetflamechocolate.com/collections/truffles, https://violetflamechocolate.com/collections/gianduia, https://violetflamechocolate.com/collections/black-sugar-toffees and https://violetflamechocolate.com/collections/exquisite-gifts and 7 others have 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 31 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'classList')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

    The homepage carries about 467 words of visible text.

2 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop”, “Create Your Gifting Order” and “Contact Us”.

  • 7 short forms

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads 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.

  • 14 cookies set on arrival

    14

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

  • 21 other companies contacted

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

Apps your storefront loads

Uppromote Affiliate · Giftship · Kor Order Limit Quantity · Timesact Pre Order · Klaviyo Email Marketing Sms · Judge Me Reviews · Savedby Package Protection · Affliate By Secomapp · Purchase Limit · Accessibly App · rechargecdn.com · Selleasy

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on violetflamechocolate.com, including 13 speed issues, 1 SEO issue and 4 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