Website review, no card needed
emmaspremiumservices.com website review
Visit site (opens in a new tab)Reviewed 5 November 202632 issues · 82 checks
This review found 32 issues worth fixing on emmaspremiumservices.com, 11 of them high impact, across 82 checks. The most urgent: main-thread work: 11.2 s. 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
66D- #114,121 of 125,033 reviewed websitesbeats 7%
- #66,997 of 70,091 online storesbeats 4%
- #61,367 of 63,699 Shopify storesbeats 3%
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.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 174 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 176 ms |
| Jun 6, 2026 | 184 ms |
| Jun 13, 2026 | 186 ms |
| Jun 20, 2026 | 189 ms |
| Jun 27, 2026 | 195 ms |
| Jul 4, 2026 | 197 ms |
| Jul 11, 2026 | 205 ms |
| Jul 18, 2026 | 201 ms |
| Jul 25, 2026 | 202 ms |
| Aug 1, 2026 | 204 ms |
| Aug 8, 2026 | 205 ms |
| Aug 15, 2026 | 213 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 223 ms |
| Sep 5, 2026 | 224 ms |
| Sep 12, 2026 | 221 ms |
| Sep 19, 2026 | 227 ms |
| Sep 26, 2026 | 230 ms |
| Oct 3, 2026 | 228 ms |
| Oct 10, 2026 | 230 ms |
| Oct 17, 2026 | 224 ms |
| Oct 24, 2026 | 222 ms |
| Oct 31, 2026 | 226 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
1.3 s
2.5 s
3.8 s
5.0 s
6.3 s
7.5 s
8.8 s
10.0 s
Speed
Main-thread work: 11.2 s
A phone's processor spends 11.2 s on main-thread work while loading, 5.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
11,139 HTML elements
The page has 11,139 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (ZenDesk, Klaviyo and Clarity and others), adding 1.9 MB and 934 ms of main-thread time.
Render-blocking requests
900 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused JavaScript
450 ms · 441 KiBAbout 441 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
ZenDesk adds 395 ms
395 msZenDesk costs a phone 395 ms of main-thread work and 439 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.
Klaviyo adds 287 ms
287 msKlaviyo costs a phone 287 ms of main-thread work and 521 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 73 ms
73 msShopify costs a phone 73 ms of main-thread work and 847 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
100 ms · 118 KiB10 images could be 118 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Reduce unused CSS
150 ms · 61 KiBAbout 61 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 189 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
100 ms · 56 KiB10 files are served with short cache lifetimes, so returning visitors download them again (56 KiB).
Legacy JavaScript
50 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 17 ms
17 msYour server sent the HTML in 17 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.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NYSDOCCS Inmate Care Packages Shop Thanksgiving Dinner”.
Time to Interactive: 16.1 s
16.1 sThe page becomes fully interactive after 16.1 s. Good is under 3.8 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 335 ms
335 msReal visitors wait 335 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
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 174 ms to 226 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.213
0.213The layout shifts by 0.213 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 718 ms
718 msReal visitors wait 718 ms for your server to start answering (75th percentile). Good is under 800 ms.
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.
Images and page weight
Page weight: 3.4 MB in 333 requests
3.4 MBYour homepage downloads 3.4 MB in 333 requests on a phone: scripts 1.5 MB (156), other files 1.0 MB (115) and images 463 KiB (25). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
0.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
36 text elements with low contrast
36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 246 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
960 internal links, 32 external
The homepage links to 960 pages on emmaspremiumservices.com and 32 external pages.
8 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Emmas Premium ships approved food, clothing, and more to NYS inmates. Fresh vegetables, snacks, books, and essentials w…”.
One H1 headline
Your main headline reads: “NYSDOCCS Inmate Care Packages”.
Title: 54 characters
Your title is a healthy 54 characters: “New York Inmate Care Packages – Emmas Premium Services”.
Canonical URL set
The canonical URL is https://emmaspremiumservices.com/.
Structured data in place
Structured data found: BreadcrumbList.
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://emmaspremiumservices.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
Text is in the HTML
Your server sends the page's text in the HTML (6,206 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://emmaspremiumservices.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://emmaspremiumservices.com/pages/order-tracking has 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 197 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 “NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "price-range" has already been used …”.
2 checks passed
Tap targets are thumb-sized
281 of 300 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 8-field form
Your longest form asks for 8 fields (0 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 4,821 words of copy
The homepage carries about 4,821 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Thanksgiving Dinner”.
33 calls to action
The homepage has 33 calls to action, for example “Track Your Order”, “[email protected]” and “Downloadable Order Form”.
Social proof on the page
Social proof on the homepage: 201 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Microsoft Clarity.
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, Klaviyo and Meta Pixel 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
41 other companies contacted
Loading the homepage contacts 41 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 emmaspremiumservices.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Frequently Bought · W3 Custom Order Status · Tapcart Mobile App · Judge Me Reviews · Microsoft Clarity · Klaviyo Email Marketing Sms · recovermycart.com · w3apps.co · b-cdn.net · googleapis.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on emmaspremiumservices.com, including 19 speed issues 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.