Website review, no card needed
ocoza.com website review
Visit site (opens in a new tab)Reviewed 9 November 202622 issues · 70 checks
This review found 22 issues worth fixing on ocoza.com, 9 of them high impact, across 70 checks. The most urgent: page weight: 5.1 MB in 376 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
91A- #1,317 of 101,833 reviewed websitesbeats 98%
- #586 of 56,448 online storesbeats 98%
- #560 of 51,320 Shopify storesbeats 98%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
3,614 HTML elements
The page has 3,614 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
100 ms · 688 KiB23 images could be 688 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.
Render-blocking requests
500 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 499 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 130 ms
130 msShopify costs a phone 130 ms of main-thread work and 613 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 JavaScript
243 KiBAbout 243 KiB of JavaScript is downloaded but never used on this page.
2 third-party services on the page
2 third-party services load with your homepage (Shopify and shop.app), adding 660 KiB and 134 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
16 KiB5 files are served with short cache lifetimes, so returning visitors download them again (16 KiB).
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90. That is in Google's “good” band (90 and up).
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 9.5 s
9.5 sThe page becomes fully interactive after 9.5 s. Good is under 3.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday Special Offer: 50% off all our products”. Most of its time is resource load delay (1.8 s).
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.
3 checks passed
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Total Blocking Time: 5 ms
5 msScripts block the page for only 5 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.1 MB in 376 requests
5.1 MBYour homepage downloads 5.1 MB in 376 requests on a phone: images 3.5 MB (137), other files 769 KiB (104) and scripts 675 KiB (104). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Kis_avlusunda_iki_zarif_model.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
4 images far larger than shown
145 KiB4 images are downloaded at several times the size a phone draws them, for example Kis_avlusunda_iki_zarif_model.png at 1,080 px wide, shown at 332 px. Resized copies would save about 145 KiB.
1 image below the first screen load straight away
1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 173.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
33 tap targets too small
33 tap targets are too small or too close together to hit reliably with a finger.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 161 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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
315 internal links, 0 external
The homepage links to 315 pages on ocoza.com and 0 external pages.
8 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Shop women's and men's fashion at Ocoza: dresses, homewear, underwear and more from selected brands. Shipping from the …”.
One H1 headline
Your main headline reads: “– Women's & Men's Fashion Online”.
Title: 38 characters
Your title is a healthy 38 characters: “Ocoza – Women's & Men's Fashion Online”.
Canonical URL set
The canonical URL is https://ocoza.com/en.
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.
XML sitemap found
Your XML sitemap is reachable at https://ocoza.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (1,470 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ocoza.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 linked pages hidden from search
https://ocoza.com/en/collections/womens-fashion, https://ocoza.com/en/collections/dresses, https://ocoza.com/en/collections/evening-gowns, https://ocoza.com/en/collections/blouses-shirts, https://ocoza.com/en/collections/damen-t-shirts and https://ocoza.com/en/collections/damen-hosen and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages without a meta description
https://ocoza.com/en/collections/damen-t-shirts, https://ocoza.com/en/collections/damen-hosen, https://ocoza.com/en/collections/damen-shorts and https://ocoza.com/en/collections/damen-jacken-maentel 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 150 found) and read each the way a search engine does.
5 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.
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
61 of 71 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 887 words of copy
The homepage carries about 887 words of visible text.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “Contact information”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 12 customer or partner logos and 1 trust badge.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
10 other companies contacted
Loading the homepage contacts 10 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 ocoza.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Forms
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
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Berlin
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on ocoza.com, including 8 speed issues and 2 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.