Website review, no card needed
thepretzelcompany.com website review
Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 86 checks
This review found 33 issues worth fixing on thepretzelcompany.com, 10 of them high impact, across 86 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
Site score
85B- #16,989 of 126,458 reviewed websitesbeats 82%
- #10,556 of 70,479 online storesbeats 80%
- #10,241 of 63,972 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 146 ms |
| May 23, 2026 | 150 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 156 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 152 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 147 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 146 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
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.3 s
5.0 s
5.7 s
Speed
Reduce unused JavaScript
1.4 s · 769 KiBAbout 769 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Main-thread work: 9.0 s
A phone's processor spends 9.0 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,602 HTML elements
The page has 3,602 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 (Shopify, Clarity and Judge.me and others), adding 2.2 MB and 1.2 s of main-thread time.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
50 ms · 455 KiB14 images could be 455 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.
Shopify adds 338 ms
338 msShopify costs a phone 338 ms of main-thread work and 1.2 MB 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.
Clarity adds 266 ms
266 msClarity costs a phone 266 ms of main-thread work and 29 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.
Judge.me adds 182 ms
182 msJudge.me costs a phone 182 ms of main-thread work and 369 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
150 ms · 235 KiB17 files are served with short cache lifetimes, so returning visitors download them again (235 KiB).
Legacy JavaScript
150 ms · 51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
200 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 179 ms. During a long task the page ignores taps.
Reduce unused CSS
52 KiBAbout 52 KiB of CSS is downloaded but never applied on this page.
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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
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: 18.6 s
18.6 sYour largest element takes 18.6 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: 20.2 s
20.2 sThe page becomes fully interactive after 20.2 s. Good is under 3.8 s.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 404 ms
404 msScripts block taps and scrolling for 404 ms in total while the page loads. Good is under 200 ms.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 625 ms
625 msReal visitors wait 625 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 17.6 MB in 423 requests
17.6 MBYour homepage downloads 17.6 MB in 423 requests on a phone: media 10.9 MB (1), images 2.9 MB (49) and scripts 1.9 MB (150). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
transparentbgpretzel_8db42995-5e09-483a-936a-4a95b49fad81.pn 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 far larger than shown
440 KiB1 image is downloaded at several times the size a phone draws it, for example transparentbgpretzel_8db42995-5e09-483a-936a-4a95b49fad81.pn at 3,024 px wide, shown at 200 px. Resized copies would save about 440 KiB.
1 image in older formats
1 image (261 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.
About 5.0 g of CO₂ per visit
4.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.99 g of CO₂e: 598.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
32 text elements with low contrast
32 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.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (91 characters)
Your title is 91 characters, so Google will cut it off around 60: “THE PRETZEL COMPANY | the best handmade soft pretzels. shipped fresh. – The Pretzel Compa…”.
2 H1 headlines
There are 2 <h1> headlines (“” and “the signature box – 8 soft pretzels”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization, Product and WebSite) but with 1 problem, for example “Product: image is not an absolute URL ("https:files/DSC07229.jpg")”.
74 internal links, 16 external
The homepage links to 74 pages on thepretzelcompany.com and 16 external pages.
5 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “MADE RIGHT. handmade soft pretzels. simple ingredients. hand-twisted and shipped fresh to your door nationwide. the bes…”.
Canonical URL set
The canonical URL is https://thepretzelcompany.com/.
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://thepretzelcompany.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
44%The HTML your server sends has 1,164 of the 2,624 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
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.
llms.txt published
The site publishes https://thepretzelcompany.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://thepretzelcompany.com/products/signature-box has 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 33 found) and read each the way a search engine does.
6 checks passed
Linked pages load
6 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 6 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 6 pages that loaded have a <title>.
Best practices
29 small tap targets
29 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 2,624 words of copy
The homepage carries about 2,624 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “shop pretzels”.
10 calls to action
The homepage has 10 calls to action, for example “order our signature pretzels”, “shop by collection” and “contact us”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 6 customer or partner logos, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
48 other companies contacted
Loading the homepage contacts 48 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 thepretzelcompany.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Venon · Judge Me Reviews · Eg Auto Add To Cart · Klaviyo Email Marketing Sms · Microsoft Clarity · Forms · Countdown Timer · Post Purchase · Restockrocket · trafficmanager.net · good-apps.co
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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on thepretzelcompany.com, including 14 speed issues and 3 SEO issues. 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.