Website review, no card needed
thedirtycookieoc.com website review
Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 88 checks
This review found 38 issues worth fixing on thedirtycookieoc.com, 12 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
74C- #82,783 of 117,865 reviewed websitesbeats 26%
- #52,465 of 67,000 online storesbeats 18%
- #49,378 of 61,088 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 131 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 148 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 137 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 168 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 148 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 150 ms |
| Oct 24, 2026 | 162 ms |
| Oct 31, 2026 | 169 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.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Render-blocking requests
1.3 s24 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Shopify adds 1.0 s
1.0 sShopify costs a phone 1.0 s of main-thread work and 514 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and Google CDN and others), adding 1.8 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
300 ms · 980 KiBAbout 980 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 486 ms
486 msGoogle Tag Manager costs a phone 486 ms of main-thread work and 473 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.
2,699 HTML elements
The page has 2,699 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 183 ms
183 msGoogle CDN costs a phone 183 ms of main-thread work and 301 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 210 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
168 KiB13 files are served with short cache lifetimes, so returning visitors download them again (168 KiB).
Improve image delivery
95 KiB2 images could be 95 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need.
Reduce unused CSS
29 KiBAbout 29 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.
1 checks passed
Server response: 22 ms
22 msYour server sent the HTML in 22 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 909 ms
909 msScripts block taps and scrolling for 909 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You Only Get One Shot… To Impress with the Ultimate Gift ✨”. Most of its time is element render delay (2.5 s).
Real-user INP: 212 ms
212 msReal visitors wait 212 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 131 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.163
0.163The layout shifts by 0.163 while loading, so content jumps under the reader's thumb. Good is under 0.1.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 387 ms
387 msReal visitors wait 387 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 3.3 MB in 219 requests
3.3 MBYour homepage downloads 3.3 MB in 219 requests on a phone: scripts 1.9 MB (82), other files 692 KiB (74) and images 507 KiB (20). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
haunted-gingerbread-house-2_170x.jpg 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
17 KiB1 image is downloaded at several times the size a phone draws it, for example banner-900.gif at 1,200 px wide, shown at 390 px. Resized copies would save about 17 KiB.
1 image in older formats
1 image (342 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 0.9 g of CO₂ per visit
0.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 113.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
36 form fields without a label
36 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 78 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 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Gourmet Cookie Gifts | Cookie Shots Stuffed Cookies | Dirty Cookie”.
147 internal links, 7 external
The homepage links to 147 pages on thedirtycookieoc.com and 7 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Send gourmet cookie gifts nationwide! Try Dirty Cookie’s viral Cookie Shots—made to fill with milk, coffee, or booze—pl…”.
One H1 headline
Your main headline reads: “The Dirty Cookie”.
Canonical URL set
The canonical URL is https://www.dirtycookie.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://www.dirtycookie.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.dirtycookie.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,096 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.dirtycookie.com/pages/corporate-gifting-events-parties, which answers with an error. Visitors hit a dead end and search engines drop it.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
6 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=283023875&tm=gtm002&Ver=2&mid=a64bb506-d096-4ed1-81bd-7848b5626427&bo=1&sid=9d350950db4211f1818b6f903ff19535&vid=9d352b20db4211f19fa491d7821a6d55&vids=1&msclkid=N>m_.
4 small tap targets
4 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 132 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 25-field form
Your longest form asks for 25 fields (0 required). Every extra field lowers completion.
Only about 184 words
The homepage has only about 184 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP THE DIRTY 10” and “SHOP NOW”.
22 calls to action
The homepage has 22 calls to action, for example “Shop”, “Go to Shop” and “Shop By Category”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies, 3 of them by other companies (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.
36 other companies contacted
Loading the homepage contacts 36 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 thedirtycookieoc.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Vo Product Options · Judge Me Reviews · Forms · postscript.io · 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
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on thedirtycookieoc.com, including 19 speed issues, 1 SEO issue and 5 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.