Website review, no card needed
priyafoods.com website review
Visit site (opens in a new tab)Reviewed 25 October 202637 issues · 85 checks
This review found 37 issues worth fixing on priyafoods.com, 10 of them high impact, across 85 checks. The most urgent: fails Core Web Vitals for real visitors. 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- #86,555 of 123,862 reviewed websitesbeats 26%
- #54,436 of 69,698 online storesbeats 18%
- #51,149 of 63,406 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.5 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 110 ms |
| May 9, 2026 | 113 ms |
| May 16, 2026 | 112 ms |
| May 23, 2026 | 115 ms |
| May 30, 2026 | 117 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 123 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 134 ms |
| Aug 8, 2026 | 140 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 159 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 167 ms |
| Sep 19, 2026 | 174 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 153 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
Speed
Main-thread work: 8.7 s
A phone's processor spends 8.7 s on main-thread work while loading, 5.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,925 HTML elements
The page has 4,925 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
500 ms · 1.1 MB52 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (minmaxify.com, Shopify and Clarity and others), adding 874 KiB and 1.1 s of main-thread time.
Mobile performance score: 59
59/100Your mobile performance score is 59 (desktop: 78). Pages that score under 90 lose visitors before the first paint.
minmaxify.com adds 614 ms
614 msminmaxify.com costs a phone 614 ms of main-thread work and 9 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.
Shopify adds 281 ms
281 msShopify costs a phone 281 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 343 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 35 KiBAbout 35 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.
Reduce unused JavaScript
137 KiBAbout 137 KiB of JavaScript is downloaded but never used on this page.
Minify JavaScript
32 KiB32 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
25 KiB6 files are served with short cache lifetimes, so returning visitors download them again (25 KiB).
Duplicated JavaScript
21 KiB21 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 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.
1 checks passed
Server response: 25 ms
25 msYour server sent the HTML in 25 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: 19.6 s
19.6 sThe page becomes fully interactive after 19.6 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 259 ms
259 msReal visitors wait 259 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 110 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 329 ms
329 msScripts block taps and scrolling for 329 ms in total while the page loads. Good is under 200 ms.
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 332 requests
5.2 MBYour homepage downloads 5.2 MB in 332 requests on a phone: images 3.3 MB (110), other files 956 KiB (103) and scripts 667 KiB (76). Under 2 MB keeps phones on slow connections fast.
24 images below the first screen load straight away
24 images further down the page (932 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
77 KiB1 image is downloaded at several times the size a phone draws it, for example Roti-pachidi-story_d8674090-096e-4359-bf1f-e9e8aaf06cd4.jpg at 1,601 px wide, shown at 390 px. Resized copies would save about 77 KiB.
2 images in older formats
2 images (167 KiB) are 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 1.5 g of CO₂ per visit
1.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.46 g of CO₂e: 175.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
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 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
42 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: 42 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
154 internal links, 25 external
The homepage links to 154 pages on priyafoods.com and 25 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Buy Indian Pickles, Masalas and Instant Mixes Online”.
Title: 64 characters
Your title is a healthy 64 characters: “Buy Indian Pickles, Masalas & Instant Mixes Online | Priya Foods”.
Canonical URL set
The canonical URL is https://priyafoods.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://priyafoods.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 (4,667 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://priyafoods.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://priyafoods.com/pages/enquiry-form and https://priyafoods.com/pages/feedback-form have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
6 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://priyafoods.com/cdn/shop/t/11/assets/block-product-variant-selector.css?v=4090' bec…”.
2 checks passed
Tap targets are thumb-sized
15 of 15 tappable elements near the top are at least 24 px.
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.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 816 words of copy
The homepage carries about 816 words of visible text.
6 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 Now”, “Shop” and “Download Brochure”.
7 short forms
7 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 107 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Opening hours shown
Your opening hours are on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
27 other companies contacted
Loading the homepage contacts 27 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 priyafoods.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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on priyafoods.com, including 20 speed issues, 2 SEO issues and 3 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.