Website review, no card needed
pomelofashion.com website review
Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 87 checks
This review found 40 issues worth fixing on pomelofashion.com, 18 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 4, 2026 | 5.6 s |
| Jul 11, 2026 | 5.9 s |
| Jul 18, 2026 | 6.3 s |
| Jul 25, 2026 | 6.4 s |
| Aug 1, 2026 | 6.5 s |
| Aug 8, 2026 | 6.1 s |
| Aug 15, 2026 | 5.6 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.5 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 4.1 s |
| Oct 31, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 4, 2026 | 211 ms |
| Jul 11, 2026 | 231 ms |
| Jul 18, 2026 | 229 ms |
| Jul 25, 2026 | 226 ms |
| Aug 1, 2026 | 229 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 219 ms |
| Aug 22, 2026 | 217 ms |
| Aug 29, 2026 | 214 ms |
| Sep 5, 2026 | 220 ms |
| Sep 12, 2026 | 214 ms |
| Sep 19, 2026 | 210 ms |
| Sep 26, 2026 | 206 ms |
| Oct 3, 2026 | 195 ms |
| Oct 10, 2026 | 188 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 183 ms |
| Oct 31, 2026 | 185 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.4 s
2.9 s
4.3 s
5.8 s
7.2 s
8.7 s
10.1 s
11.6 s
Speed
Reduce unused JavaScript
6.3 s · 999 KiBAbout 999 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 213 KiB15 files are served with short cache lifetimes, so returning visitors download them again (213 KiB).
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.1 s
A phone's processor spends 8.1 s on main-thread work while loading, 3.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 (cloudfront.net, Google CDN and Other Google APIs/SDKs and others), adding 2.6 MB and 1.6 s of main-thread time.
cloudfront.net adds 776 ms
776 mscloudfront.net costs a phone 776 ms of main-thread work and 1.2 MB 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 703 ms. During a long task the page ignores taps.
Google CDN adds 446 ms
446 msGoogle CDN costs a phone 446 ms of main-thread work and 733 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,289 HTML elements
The page has 2,289 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 47 KiBAbout 47 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.
Minify JavaScript
150 ms · 22 KiB22 KiB could be saved by minifying JavaScript.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Improve image delivery
11 KiB1 image could be 11 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Duplicated JavaScript
6 KiB6 KiB JavaScript is shipped twice across bundles.
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: 19 ms
19 msYour server sent the HTML in 19 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: 18.8 s
18.8 sYour largest element takes 18.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 21.6 s
21.6 sThe page becomes fully interactive after 21.6 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
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 TTFB: 811 ms
811 msReal visitors wait 811 ms for your server to start answering (75th percentile). Good is under 800 ms.
7 checks passed
Real-user INP: 174 ms
174 msReal visitors wait 174 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 211 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.6 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.025
0.025The layout barely moves while loading (CLS 0.025, good is under 0.1).
Images and page weight
Page weight: 12.9 MB in 161 requests
12.9 MBYour homepage downloads 12.9 MB in 161 requests on a phone: media 9.3 MB (1), scripts 2.2 MB (38) and images 565 KiB (42). Under 2 MB keeps phones on slow connections fast.
About 3.7 g of CO₂ per visit
3.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.66 g of CO₂e: 439.7 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
158 text elements with low contrast
158 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
ARIA commands must have an accessible name (3 elements)
ARIA commands must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 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.
2 form fields without a label
2 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 should not be empty (5 elements)
Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “POMELO Fashion | Get all the latest fashion, updated twice every week! - Pomelo”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
12 internal links, 7 external
The homepage links to 12 pages on pomelofashion.com and 7 external pages.
5 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Shop the latest fashion at POMELO fashion. Designed and manufactured in house for quality and style. Dresses, tops, kni…”.
Canonical URL set
The canonical URL is https://www.pomelofashion.com/us/en/.
Structured data in place
Structured data found: Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://pomelo-web-s3.pomelofashion.com/static/sitemaps-v5/pomelo_index_sitemap.xml.
AI search readiness
robots.txt blocks 3 AI answer engine crawlers
3 of 6Your robots.txt shuts out Claude search (Claude-SearchBot), Claude (Claude-User) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Most text only appears after JavaScript runs
3%A phone browser shows 825 words, but the HTML your server sends has only 28. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No llms.txt
There is no https://www.pomelofashion.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.
Opted out of AI training for 2 crawlers
robots.txt blocks Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
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.
Other pages
11 pages share a title
https://www.pomelofashion.com/us/en, https://www.pomelofashion.com/us/en/about, https://www.pomelofashion.com/us/en/info/contact, https://www.pomelofashion.com/us/en/press, https://www.pomelofashion.com/us/en/info/shipping and https://www.pomelofashion.com/us/en/info/returns and 5 others all use the title “POMELO Fashion | Get all the latest fashion, updated twice every week…”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages share a meta description
https://www.pomelofashion.com/us/en/about, https://www.pomelofashion.com/us/en/info/contact, https://www.pomelofashion.com/us/en/press, https://www.pomelofashion.com/us/en/info/shipping, https://www.pomelofashion.com/us/en/info/returns and https://www.pomelofashion.com/us/en/info/faq and 4 others use the same meta description. A description written for each page earns more clicks.
9 pages without an H1
https://www.pomelofashion.com/us/en/info/contact, https://www.pomelofashion.com/us/en/press, https://www.pomelofashion.com/us/en/info/shipping, https://www.pomelofashion.com/us/en/info/returns, https://www.pomelofashion.com/us/en/info/faq and https://www.pomelofashion.com/us/en/ttb-home and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://www.pomelofashion.com/us/en/info/contact, https://www.pomelofashion.com/us/en/press, https://www.pomelofashion.com/us/en/info/shipping, https://www.pomelofashion.com/us/en/info/returns, https://www.pomelofashion.com/us/en/info/faq and https://www.pomelofashion.com/us/en/info/privacy-policy and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 10 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 10 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
23 small tap targets
23 of 74 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 825 words of copy
The homepage carries about 825 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “Tap.Try.Buy.”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
20 other companies contacted
Loading the homepage contacts 20 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 pomelofashion.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on pomelofashion.com, including 16 speed issues, 3 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.