Website review, no card needed
zoey.ph website review
Visit site (opens in a new tab)Reviewed 8 November 202630 issues · 80 checks
This review found 30 issues worth fixing on zoey.ph, 8 of them high impact, across 80 checks. The most urgent: invalid ARIA attributes. 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
84B- #19,252 of 105,912 reviewed websitesbeats 77%
- #12,460 of 59,635 online storesbeats 73%
- #12,098 of 54,359 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 95 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 102 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 109 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 111 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 109 ms |
| Aug 15, 2026 | 110 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 122 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 105 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 105 ms |
| Oct 31, 2026 | 105 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
Render-blocking requests
800 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Reduce unused CSS
300 ms · 41 KiBAbout 41 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.
Improve image delivery
150 ms · 29 KiB2 images could be 29 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
80 KiBAbout 80 KiB of JavaScript is downloaded but never used on this page.
3 third-party services on the page
3 third-party services load with your homepage (Shopify, Bugsnag and kaizenbrands.com), adding 77 KiB and 34 ms of main-thread time.
Use efficient cache lifetimes
37 KiB3 files are served with short cache lifetimes, so returning visitors download them again (37 KiB).
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 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.
3 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92. That is in Google's “good” band (90 and up).
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 378 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest content (LCP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.3 s
3.3 sYour largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 98 ms
98 msReal visitors wait 98 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 689 ms
689 msReal visitors wait 689 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 3.3 s
3.3 sThe page is fully interactive after 3.3 s.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Speed Index: 1.9 s
1.9 sVisually, the page fills in at 1.9 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.5 MB in 175 requests
1.5 MBYour homepage downloads 1.5 MB in 175 requests on a phone: other files 856 KiB (127), scripts 378 KiB (36) and images 176 KiB (5). That is a lean page.
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
24 elements use ARIA attributes their role does not allow, which confuses screen readers.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (66 elements)
All page content should be contained by landmarks: 66 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.
32 links without text
32 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://zoey.ph/search?q={search_term_string}")”.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
126 internal links, 6 external
The homepage links to 126 pages on zoey.ph and 6 external pages.
4 checks passed
Title: 62 characters
Your title is a healthy 62 characters: “Wedding Rings Philippines, Engagement Rings Philippines - Zoey”.
Canonical URL set
The canonical URL is https://zoey.ph/.
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://zoey.ph/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 (838 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://zoey.ph/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://zoey.ph/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://zoey.ph/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
10 pages without a meta description
https://zoey.ph/collections/wedding-rings, https://zoey.ph/collections/mens-rings, https://zoey.ph/collections/tungsten-carbide, https://zoey.ph/collections/engagement-rings, https://zoey.ph/collections/sterling-silver-rings and https://zoey.ph/collections/necklaces and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://zoey.ph/collections/best-sellers/products/brilliant-halo-in-ruby-titanium-engagement-ring, whose canonical is https://zoey.ph/products/brilliant-halo-in-ruby-titanium-engagement-ring. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
10 pages without an H1
https://zoey.ph/collections/wedding-rings, https://zoey.ph/collections/mens-rings, https://zoey.ph/collections/tungsten-carbide, https://zoey.ph/collections/engagement-rings, https://zoey.ph/collections/sterling-silver-rings and https://zoey.ph/collections/gra-moissanite-engagement-rings and 4 others have 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 45 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://sst.zoey.ph/g/collect?v=2&tid=G-48CRQWNY3D>m=45je6b41v9228787059z89247902153za20gzb924790…”.
2 checks passed
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 279 words of copy
The homepage carries about 279 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Sign Up” and “Contact Us”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
12 other companies contacted
Loading the homepage contacts 12 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 zoey.ph, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on zoey.ph, including 5 speed issues, 4 SEO issues and 4 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.