Website review, no card needed
toffeetogo.com website review
Visit site (opens in a new tab)Reviewed 6 November 202619 issues · 68 checks
This review found 19 issues worth fixing on toffeetogo.com, 7 of them high impact, across 68 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
1.3 s · 309 KiBAbout 309 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
700 ms · 99 KiB7 files are served with short cache lifetimes, so returning visitors download them again (99 KiB).
Improve image delivery
300 ms · 161 KiB7 images could be 161 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 28 ms
28 msShopify costs a phone 28 ms of main-thread work and 457 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.
5 third-party services on the page
5 third-party services load with your homepage (Hubspot, Google CDN and Shopify and others), adding 626 KiB and 138 ms of main-thread time.
Legacy JavaScript
150 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 60 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 402 ms of it running JavaScript. That is comfortably low.
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.2 s
10.2 sYour largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sweet Holiday Gifts! Spread a little holiday joy with our h…”.
Time to Interactive: 10.4 s
10.4 sThe page becomes fully interactive after 10.4 s. Good is under 3.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
4 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 FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 15 ms
15 msScripts block the page for only 15 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.4 MB in 178 requests
2.4 MBYour homepage downloads 2.4 MB in 178 requests on a phone: images 933 KiB (28), other files 724 KiB (79) and scripts 590 KiB (45). Under 2 MB keeps phones on slow connections fast.
4 images below the first screen load straight away
4 images further down the page (219 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 82.7 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
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
47 internal links, 8 external
The homepage links to 47 pages on toffeetogo.com and 8 external pages.
7 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “Oprah's Favorite in 2013. Shop handcrafted small batch toffee — perfect for gifts, corporate orders, and treating yours…”.
Title: 45 characters
Your title is a healthy 45 characters: “Toffee to Go | Handcrafted Small Batch Toffee”.
Canonical URL set
The canonical URL is https://toffeetogo.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.
XML sitemap found
Your XML sitemap is reachable at https://toffeetogo.com/sitemap.xml.
AI search readiness
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,218 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://toffeetogo.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without an H1
https://toffeetogo.com/products/assorted-toffee, https://toffeetogo.com/products/milk-chocolate-toffee, https://toffeetogo.com/products/dark-chocolate-toffee, https://toffeetogo.com/products/white-chocolate-toffee, https://toffeetogo.com/pages/corporate-gifts and https://toffeetogo.com/pages/insurance-client-gifts and 8 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 16 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
13 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 13-field form
Your longest form asks for 13 fields (9 required). Every extra field lowers completion.
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 707 words of copy
The homepage carries about 707 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: “Shop Now”.
11 calls to action
The homepage has 11 calls to action, for example “Shop Toffee”, “Call 813-605-0655” and “Shop Now”.
Analytics in place
Analytics detected: HubSpot.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
15 cookies set on arrival
15Opening the homepage sets 15 cookies (measured from a US location before any click).
31 other companies contacted
Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 toffeetogo.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Powerful Form Builder · Forms · Essential Icon Badge Banners · hubapi.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
- The footer still says © 2023.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Pinellas Park
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on toffeetogo.com, including 10 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.