Website review, no card needed
orolosangeles.com website review
Visit site (opens in a new tab)Reviewed 17 November 202640 issues · 86 checks
This review found 40 issues worth fixing on orolosangeles.com, 16 of them high impact, across 86 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
78C- #58,701 of 115,630 reviewed websitesbeats 44%
- #38,963 of 66,528 online storesbeats 36%
- #37,294 of 60,792 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 182 ms |
| Jun 13, 2026 | 190 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 191 ms |
| Jul 4, 2026 | 184 ms |
| Jul 11, 2026 | 187 ms |
| Jul 18, 2026 | 196 ms |
| Jul 25, 2026 | 188 ms |
| Aug 1, 2026 | 189 ms |
| Aug 8, 2026 | 194 ms |
| Aug 15, 2026 | 193 ms |
| Aug 22, 2026 | 204 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 236 ms |
| Sep 12, 2026 | 236 ms |
| Sep 19, 2026 | 211 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 182 ms |
| Oct 24, 2026 | 188 ms |
| Oct 31, 2026 | 180 ms |
| Nov 7, 2026 | 208 ms |
| Nov 14, 2026 | 200 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
0.6 s
1.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.4 s
5.1 s
Speed
Reduce unused JavaScript
6.6 s · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.6 s faster on a phone.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 3.1 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 (YouTube, Google Tag Manager and Facebook and others), adding 3.7 MB and 1.9 s of main-thread time.
Use efficient cache lifetimes
650 ms · 566 KiB38 files are served with short cache lifetimes, so returning visitors download them again (566 KiB).
Improve image delivery
50 ms · 904 KiB13 images could be 904 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
YouTube adds 703 ms
703 msYouTube costs a phone 703 ms of main-thread work and 2.0 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.
Google Tag Manager adds 511 ms
511 msGoogle Tag Manager costs a phone 511 ms of main-thread work and 707 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 CSS
300 ms · 109 KiBAbout 109 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.
Render-blocking requests
300 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 218 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 23.7 s
23.7 sYour largest element takes 23.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 16.7 s
16.7 sVisually, the page fills in at 16.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 45.9 s
45.9 sThe page becomes fully interactive after 45.9 s. Good is under 3.8 s.
First Contentful Paint: 7.1 s
7.1 sThe first text or image appears after 7.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 627 ms
627 msScripts block taps and scrolling for 627 ms in total while the page loads. Good is under 200 ms.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 180 ms to 200 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.7 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: 8.6 MB in 415 requests
8.6 MBYour homepage downloads 8.6 MB in 415 requests on a phone: scripts 4.4 MB (107), images 2.4 MB (31) and other files 1.4 MB (254). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
282 KiB3 images are downloaded at several times the size a phone draws them, for example Mask_group.jpg at 1,000 px wide, shown at 165 px. Resized copies would save about 282 KiB.
3 images below the first screen load straight away
3 images further down the page (239 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.44 g of CO₂e: 292.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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA toggle fields must have an accessible name (3 elements)
ARIA toggle fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has 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 (h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “ORO Los Angeles”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “STAPLE SILHOUETTES, SIGNATURE GARMENTS, AND HANDC…”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (ClothingStore, Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.orolosangeles.com")”.
109 internal links, 4 external
The homepage links to 109 pages on orolosangeles.com and 4 external pages.
5 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Shop the Official Online ORO Los Angeles store for a variety of high-end ready-to-wear, footwear, leather goods, and ac…”.
Canonical URL set
The canonical URL is https://www.orolosangeles.com/.
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://www.orolosangeles.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (943 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.orolosangeles.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://www.orolosangeles.com/collections/sample-sale and https://www.orolosangeles.com/collections/hats have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.orolosangeles.com/collections/shoes, https://www.orolosangeles.com/collections/pants, https://www.orolosangeles.com/collections/latestcollection, https://www.orolosangeles.com/collections/sale, https://www.orolosangeles.com/collections/shirts and https://www.orolosangeles.com/collections/all-products and 9 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 35 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.
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
5 broken images
5 images failed to load on a phone, for example https://formsv2.soundestlink.com/forms/1560/67bf29081d8320e6e6e30dc7.
9 third-party cookies
9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
31 of 33 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 341 words of copy
The homepage carries about 341 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: “Learn more” and “SHOP LATEST COLLECTION”.
13 calls to action
The homepage has 13 calls to action, for example “SHOP expand”, “SHOP INSTAGRAM” and “SHOP LATEST COLLECTION”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks and “OVER 100,000 CUSTOMERS”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
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.
34 cookies set on arrival
34Opening the homepage sets 34 cookies, 4 of them by other companies (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.
55 other companies contacted
Loading the homepage contacts 55 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 orolosangeles.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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Elevar Conversion Tracking · Seo Manager Venntov · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Omnisend · privy.com · stamped.io · gatsby.tech · dualsidedapp.com · avada.io · gorgias.chat · cloudfront.net · backinstock.org · 9gtb.com · amazonaws.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
- Gatsby
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Huntington Beach
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 orolosangeles.com, including 18 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.