Website review, no card needed
electricandrose.com website review
Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 81 checks
This review found 32 issues worth fixing on electricandrose.com, 12 of them high impact, across 81 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
76C- #72,353 of 118,456 reviewed websitesbeats 34%
- #46,681 of 67,291 online storesbeats 26%
- #44,282 of 61,352 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 79 ms |
| May 23, 2026 | 80 ms |
| May 30, 2026 | 80 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 90 ms |
| Jul 11, 2026 | 89 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 90 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 84 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 92 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 106 ms |
| Oct 24, 2026 | 108 ms |
| Oct 31, 2026 | 104 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.2 s · 814 KiBAbout 814 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Improve image delivery
1.7 s · 1.0 MB22 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.
Use efficient cache lifetimes
1.8 s · 523 KiB16 files are served with short cache lifetimes, so returning visitors download them again (523 KiB).
Mobile performance score: 44
44/100Your mobile performance score is 44. 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 (Yotpo, Accessibe Accessibility Overlay and joinground.com and others), adding 1.3 MB and 836 ms of main-thread time.
Render-blocking requests
950 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 88 KiBAbout 88 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 · 39 KiB39 KiB could be saved by minifying JavaScript.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.0 s
16.0 sYour largest element takes 16.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.805
0.805The layout shifts by 0.805 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 79 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
8 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 102 ms
102 msReal visitors wait 102 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 379 ms
379 msReal visitors wait 379 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 175 ms
175 msScripts block the page for only 175 ms while loading. Good is under 200 ms.
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.
Images and page weight
Page weight: 4.7 MB in 233 requests
4.7 MBYour homepage downloads 4.7 MB in 233 requests on a phone: images 2.2 MB (34), scripts 1.6 MB (75) and other files 781 KiB (107). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
3_c26d37b3-a72a-4ce6-956c-5935fca69bf0.jpg 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).
1 image below the first screen load straight away
1 image further down the page (38 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.33 g of CO₂e: 159.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
7 images without alt text
7 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.
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.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
106 internal links, 2 external
The homepage links to 106 pages on electricandrose.com and 2 external pages.
5 checks passed
Meta description: 94 characters
Your meta description is 94 characters: “Coastal style, crafted by women who live it. 1% of all sales donated to protecting our oceans.”.
Title: 60 characters
Your title is a healthy 60 characters: “Coastal Lifestyle Clothing Brand. – Electric & Rose Clothing”.
Canonical URL set
The canonical URL is https://electricandrose.com/.
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://electricandrose.com/sitemap.xml.
AI search readiness
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
llms.txt published
The site publishes https://electricandrose.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages without a meta description
https://electricandrose.com/collections/winter-1-26, https://electricandrose.com/collections/core, https://electricandrose.com/collections/made-in-la, https://electricandrose.com/collections/erins-picks, https://electricandrose.com/collections/100-cotton and https://electricandrose.com/collections/sport-bras and 2 others 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 51 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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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 ()”.
2 checks passed
Tap targets are thumb-sized
30 of 37 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 128 words
The homepage has only about 128 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL”.
8 calls to action
The homepage has 8 calls to action, for example “SHOP ALL”, “Contact” and “Return/Exchange Request”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
42 other companies contacted
Loading the homepage contacts 42 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 electricandrose.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Wair Size Fit Recommendation · Yotpo Product Reviews · Yotpo Loyalty Rewards · Klaviyo Email Marketing Sms · Ground · Redo · Back In Stock · shareasale.com · dailykarma.io
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
- Los Angeles
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 electricandrose.com, including 13 speed issues, 3 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.