Website review, no card needed
kooshigourmet.com website review
Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 79 checks
This review found 31 issues worth fixing on kooshigourmet.com, 12 of them high impact, across 79 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
86B- #11,747 of 120,300 reviewed websitesbeats 86%
- #7,179 of 68,126 online storesbeats 85%
- #6,956 of 62,084 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.0 s
2.1 s
3.1 s
4.1 s
5.2 s
6.2 s
7.2 s
8.2 s
Speed
Render-blocking requests
2.3 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Main-thread work: 4.1 s
A phone's processor spends 4.1 s on main-thread work while loading, 2.2 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 (Google Tag Manager, ContentSquare and Shopify and others), adding 2.5 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
460 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 512 ms
512 msGoogle Tag Manager costs a phone 512 ms of main-thread work and 925 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.
Improve image delivery
431 KiB5 images could be 431 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
ContentSquare adds 274 ms
274 msContentSquare costs a phone 274 ms of main-thread work and 185 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
279 KiB17 files are served with short cache lifetimes, so returning visitors download them again (279 KiB).
Shopify adds 178 ms
178 msShopify costs a phone 178 ms of main-thread work and 414 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,840 HTML elements
The page has 1,840 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 111 ms
111 msKlaviyo costs a phone 111 ms of main-thread work and 332 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.
ZenDesk adds 94 ms
94 msZenDesk costs a phone 94 ms of main-thread work and 386 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
150 ms · 43 KiBAbout 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 163 ms. During a long task the page ignores taps.
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 17.7 s
17.7 sVisually, the page fills in at 17.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 35.6 s
35.6 sThe page becomes fully interactive after 35.6 s. Good is under 3.8 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Chef-prepared meals, designed around how you live.”. Most of its time is element render delay (2.4 s).
Total Blocking Time: 273 ms
273 msScripts block taps and scrolling for 273 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 8.7 MB in 351 requests
8.7 MBYour homepage downloads 8.7 MB in 351 requests on a phone: images 4.5 MB (32), scripts 2.7 MB (113) and other files 898 KiB (158). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 2.9 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
2.9 MB7 images are downloaded at several times the size a phone draws them, for example KG_H_pro-090.jpg at 3,251 px wide, shown at 330 px. Resized copies would save about 2.9 MB.
9 images below the first screen load straight away
9 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (364 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 2.5 g of CO₂ per visit
2.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.46 g of CO₂e: 294.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
29 text elements with low contrast
29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 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.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and 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. (1 element).
1 checks passed
54 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: 54 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
85 internal links, 8 external
The homepage links to 85 pages on kooshigourmet.com and 8 external pages.
8 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Prepared meal delivery in Los Angeles just got easier. Enjoy organic meal prep delivery with healthy, fresh, gourmet me…”.
One H1 headline
Your main headline reads: “Chef Prepared, Organic, and Gluten-Free Meals Delivered Daily.”.
Title: 53 characters
Your title is a healthy 53 characters: “Organic Meal Delivery in Los Angeles - Kooshi Gourmet”.
Canonical URL set
The canonical URL is https://www.kooshigourmet.com/.
Structured data in place
Structured data found: FAQPage, 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.kooshigourmet.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 (2,232 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.kooshigourmet.com/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 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 15 pages 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 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 1,244 words of copy
The homepage carries about 1,244 words of visible text.
5 checks passed
8 calls to action
The homepage has 8 calls to action, for example “CONTACT”, “Get Started →” and “Shop Now”.
12 short forms
12 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 27 testimonial or review blocks, 4 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies, 2 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.
42 other companies contacted
Loading the homepage contacts 42 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 kooshigourmet.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Gempages Builder · Pagefly Ai Page Builder · Optis Product Options · amazonaws.com · postscript.io
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
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Headquarters
- West Hollywood
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on kooshigourmet.com, including 19 speed issues, 1 SEO issue and 1 conversion gap. 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.