Website review, no card needed

cinnaholic.com logo

cinnaholic.com website review

Visit site (opens in a new tab)Reviewed 18 November 202627 issues · 82 checks

This review found 27 issues worth fixing on cinnaholic.com, 7 of them high impact, across 82 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
1.2 s619 msMay 30Nov 14763 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026859 ms
Jun 6, 2026862 ms
Jun 13, 2026880 ms
Jun 20, 2026868 ms
Jun 27, 2026877 ms
Jul 4, 2026879 ms
Jul 11, 2026875 ms
Jul 18, 2026909 ms
Jul 25, 2026913 ms
Aug 1, 2026927 ms
Aug 8, 2026925 ms
Aug 15, 2026903 ms
Aug 22, 2026862 ms
Aug 29, 2026787 ms
Sep 5, 2026735 ms
Sep 12, 2026686 ms
Sep 19, 2026686 ms
Sep 26, 2026754 ms
Oct 3, 2026915 ms
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.0 s
Oct 31, 2026893 ms
Nov 7, 2026773 ms
Nov 14, 2026763 ms
Real-visitor tap response (INP)75th percentile, phones
107 ms78 msMay 30Nov 1498 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202682 ms
Jun 6, 202681 ms
Jun 13, 202683 ms
Jun 20, 202681 ms
Jun 27, 202682 ms
Jul 4, 202682 ms
Jul 11, 202683 ms
Jul 18, 202685 ms
Jul 25, 202686 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202686 ms
Sep 5, 202684 ms
Sep 12, 202682 ms
Sep 19, 202685 ms
Sep 26, 202687 ms
Oct 3, 202689 ms
Oct 10, 202695 ms
Oct 17, 202697 ms
Oct 24, 2026103 ms
Oct 31, 2026104 ms
Nov 7, 2026104 ms
Nov 14, 202698 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 cinnaholic.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cinnaholic.com at 0.6 s0.6 s
  2. cinnaholic.com at 1.2 s1.2 s
  3. cinnaholic.com at 1.8 s1.8 s
  4. cinnaholic.com at 2.3 s2.3 s
  5. cinnaholic.com at 2.9 s2.9 s
  6. cinnaholic.com at 3.5 s3.5 s
  7. cinnaholic.com at 4.1 s4.1 s
  8. cinnaholic.com at 4.7 s4.7 s

Speed

9 to fix63
  • Reduce unused JavaScript

    1.5 s · 579 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Facebook and others), adding 1.9 MB and 1.6 s of main-thread time.

  • Mobile performance score: 63

    63/100

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

  • audioeye.com adds 773 ms

    773 ms

    audioeye.com costs a phone 773 ms of main-thread work and 297 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 · 274 KiB

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

  • Google Tag Manager adds 329 ms

    329 ms

    Google Tag Manager costs a phone 329 ms of main-thread work and 480 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.

  • Reduce unused CSS

    300 ms · 70 KiB

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

  • Main-thread work: 3.2 s

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

  • cdn-website.com adds 193 ms

    193 ms

    cdn-website.com costs a phone 193 ms of main-thread work and 782 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.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 181 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).

  • Legacy JavaScript

    28 KiB

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 15.7 s

    15.7 s

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

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

    +24%

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

  • Total Blocking Time: 459 ms

    459 ms

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

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.2 s

    1.2 s

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

  • Real-user INP: 109 ms

    109 ms

    Real visitors wait 109 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.7 s

    0.7 s

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

  • Real-user TTFB: 497 ms

    497 ms

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

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

    -11%

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

  • Speed Index: 3.4 s

    3.4 s

    Visually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 94 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 94 requests on a phone: scripts 1.5 MB (39), images 228 KiB (23) and fonts 225 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.60 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • 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 9392
  • 15 tap targets too small

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

  • Elements must only use permitted ARIA attributes (6 elements)

    Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

  • 5 text elements with low contrast

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

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

Google 100100
  • 42 internal links, 22 external

    The homepage links to 42 pages on cinnaholic.com and 22 external pages.

8 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Cinnaholic specializes in gourmet cinnamon rolls that can be customized with over 20 frostings and toppings. All desser…”.

  • One H1 headline

    Your main headline reads: “Indulge Without Compromise!”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “CINNAHOLIC® - Gourmet Cinnamon Rolls”.

  • Canonical URL set

    The canonical URL is https://www.cinnaholic.com/.

  • Structured data in place

    Structured data found: 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://www.cinnaholic.com/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 (372 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.cinnaholic.com/llms.txt (2 KiB, 21 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.cinnaholic.com/accessibility is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without an H1

    https://www.cinnaholic.com/accessibility has no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9685
  • 17 small tap targets

    17 of 37 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 “Uncaught TypeError: Cannot read properties of undefined (reading 'register')”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 296 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “ORDER NOW”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “ORDER NOW” and “[email protected]”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

  • 19 other companies contacted

    Loading the homepage contacts 19 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 cinnaholic.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Company

Founded
2010

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on cinnaholic.com, including 13 speed issues and 2 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