Website review, no card needed
arevco.ca website review
Visit site (opens in a new tab)Reviewed 5 November 202631 issues · 81 checks
This review found 31 issues worth fixing on arevco.ca, 10 of them high impact, across 81 checks. The most urgent: mobile performance score: 49. 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
80B- #47,178 of 120,386 reviewed websitesbeats 55%
- #31,336 of 68,161 online storesbeats 48%
- #30,135 of 62,115 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 995 ms |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 972 ms |
| Jun 13, 2026 | 920 ms |
| Jun 20, 2026 | 934 ms |
| Jun 27, 2026 | 944 ms |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 977 ms |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 963 ms |
| Aug 1, 2026 | 920 ms |
| Aug 8, 2026 | 914 ms |
| Aug 15, 2026 | 947 ms |
| Aug 22, 2026 | 960 ms |
| Aug 29, 2026 | 993 ms |
| Sep 5, 2026 | 966 ms |
| Sep 12, 2026 | 891 ms |
| Sep 19, 2026 | 903 ms |
| Sep 26, 2026 | 884 ms |
| Oct 3, 2026 | 846 ms |
| Oct 10, 2026 | 844 ms |
| Oct 17, 2026 | 794 ms |
| Oct 24, 2026 | 799 ms |
| Oct 31, 2026 | 832 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 70 ms |
| May 23, 2026 | 65 ms |
| May 30, 2026 | 73 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 79 ms |
| Jun 20, 2026 | 78 ms |
| Jun 27, 2026 | 78 ms |
| Jul 4, 2026 | 66 ms |
| Jul 11, 2026 | 61 ms |
| Jul 18, 2026 | 62 ms |
| Jul 25, 2026 | 62 ms |
| Aug 1, 2026 | 62 ms |
| Aug 8, 2026 | 72 ms |
| Aug 15, 2026 | 76 ms |
| Aug 22, 2026 | 76 ms |
| Aug 29, 2026 | 81 ms |
| Sep 5, 2026 | 78 ms |
| Sep 12, 2026 | 70 ms |
| Sep 19, 2026 | 70 ms |
| Sep 26, 2026 | 65 ms |
| Oct 3, 2026 | 70 ms |
| Oct 10, 2026 | 70 ms |
| Oct 17, 2026 | 68 ms |
| Oct 24, 2026 | 69 ms |
| Oct 31, 2026 | 68 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.5 s
0.9 s
1.4 s
1.9 s
2.3 s
2.8 s
3.3 s
3.7 s
Speed
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Render-blocking requests
950 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused JavaScript
600 ms · 132 KiBAbout 132 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
2,480 HTML elements
The page has 2,480 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 545 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 29 KiBAbout 29 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.
4 third-party services on the page
4 third-party services load with your homepage (Privy, Shopify and hulkapps.com and others), adding 217 KiB and 151 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 136 ms. During a long task the page ignores taps.
Improve image delivery
66 KiB2 images could be 66 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
6 KiB4 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
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: 22.3 s
22.3 sYour largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 23.6 s
23.6 sThe page becomes fully interactive after 23.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.904
0.904The layout shifts by 0.904 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 70 ms to 68 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 62 ms
62 msReal visitors wait 62 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 300 ms
300 msReal visitors wait 300 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 92 ms
92 msScripts block the page for only 92 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: 6.6 MB in 244 requests
6.6 MBYour homepage downloads 6.6 MB in 244 requests on a phone: images 5.3 MB (94), other files 832 KiB (111) and scripts 368 KiB (32). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
POPPY_TL437012PGN_LIFESTYLE.webp 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 in older formats
4 images (255 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.9 g of CO₂ per visit
1.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.88 g of CO₂e: 225.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
26 elements hidden from screen readers can still receive keyboard focus.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
27 links without text
27 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.
2 checks passed
Every image has alt text
All 60 images in the HTML carry an alt attribute.
49 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: 49 passed and 7 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.
Meta description is long (185 characters)
Your meta description is 185 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
305 internal links, 14 external
The homepage links to 305 pages on arevco.ca and 14 external pages.
5 checks passed
Title: 47 characters
Your title is a healthy 47 characters: “Arevco Lighting Ottawa | Modern Lighting Ottawa”.
Canonical URL set
The canonical URL is https://lightingcanada.com/.
Structured data in place
Structured data found: Organization.
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://lightingcanada.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,507 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://lightingcanada.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://lightingcanada.com/shop declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://lightingcanada.com/shop all use the title “Arevco Lighting Ottawa | Modern Lighting Ottawa”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://lightingcanada.com/collections/large-pendants, https://lightingcanada.com/collections/table-and-desk-lamps and https://lightingcanada.com/collections/display-and-under-counter have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://lightingcanada.com/shop has 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 102 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
39 small tap targets
39 of 91 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 444 words of copy
The homepage carries about 444 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: “SHOP” and “CONTACT US”.
39 calls to action
The homepage has 39 calls to action, for example “SHOP”, “CONTACT US” and “Shop WEP”.
30 short forms
30 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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.
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.
11 other companies contacted
Loading the homepage contacts 11 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 arevco.ca, 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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
privy.com · hulkapps.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
- 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 31 issues on arevco.ca, including 9 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.