Website review, no card needed
rejuvenation.com website review
Visit site (opens in a new tab)Reviewed 20 November 202654 issues · 90 checks
This review found 54 issues worth fixing on rejuvenation.com, 17 of them high impact, across 90 checks. The most urgent: render-blocking 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
57FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.5 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 279 ms |
| Jun 6, 2026 | 288 ms |
| Jun 13, 2026 | 296 ms |
| Jun 20, 2026 | 296 ms |
| Jun 27, 2026 | 292 ms |
| Jul 4, 2026 | 281 ms |
| Jul 11, 2026 | 271 ms |
| Jul 18, 2026 | 263 ms |
| Jul 25, 2026 | 259 ms |
| Aug 1, 2026 | 262 ms |
| Aug 8, 2026 | 266 ms |
| Aug 15, 2026 | 270 ms |
| Aug 22, 2026 | 299 ms |
| Aug 29, 2026 | 329 ms |
| Sep 5, 2026 | 362 ms |
| Sep 12, 2026 | 395 ms |
| Sep 19, 2026 | 396 ms |
| Sep 26, 2026 | 397 ms |
| Oct 3, 2026 | 391 ms |
| Oct 10, 2026 | 385 ms |
| Oct 17, 2026 | 371 ms |
| Oct 24, 2026 | 356 ms |
| Oct 31, 2026 | 350 ms |
| Nov 7, 2026 | 341 ms |
| Nov 14, 2026 | 347 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.9 s
1.7 s
2.6 s
3.4 s
4.3 s
5.1 s
6.0 s
6.8 s
Speed
Render-blocking requests
3.0 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Reduce unused CSS
1.4 s · 374 KiBAbout 374 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Main-thread work: 10.5 s
A phone's processor spends 10.5 s on main-thread work while loading, 6.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 12
12/100Your mobile performance score is 12. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
450 ms · 3.1 MBAbout 3.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, site.com and Quantum Metric and others), adding 5.7 MB and 1.8 s of main-thread time.
Use efficient cache lifetimes
600 ms · 1.0 MB42 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Improve image delivery
1.2 MB21 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 573 ms. During a long task the page ignores taps.
Google Tag Manager adds 443 ms
443 msGoogle Tag Manager costs a phone 443 ms of main-thread work and 667 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.
Legacy JavaScript
300 ms · 174 KiBPolyfills for old browsers add 174 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
site.com adds 318 ms
318 mssite.com costs a phone 318 ms of main-thread work and 1.5 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.
Vimeo adds 85 ms
85 msVimeo costs a phone 85 ms of main-thread work and 2.9 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.
Quantum Metric adds 317 ms
317 msQuantum Metric costs a phone 317 ms of main-thread work and 112 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.
Tealium adds 263 ms
263 msTealium costs a phone 263 ms of main-thread work and 200 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,228 HTML elements
The page has 2,228 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
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: 48 ms
48 msYour server sent the HTML in 48 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.
Time to Interactive: 54.6 s
54.6 sThe page becomes fully interactive after 54.6 s. Good is under 3.8 s.
Largest Contentful Paint: 9.4 s
9.4 sYour largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “https://player.vimeo.com/video/1236706866”.
Speed Index: 14.7 s
14.7 sVisually, the page fills in at 14.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 3.0 s
3.0 sScripts block taps and scrolling for 3.0 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.346
0.346The layout shifts by 0.346 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 224 ms
224 msReal visitors wait 224 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 279 ms to 347 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 13.2 MB in 233 requests
13.2 MBYour homepage downloads 13.2 MB in 233 requests on a phone: scripts 6.2 MB (72), other files 4.2 MB (87) and images 2.0 MB (54). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
001.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).
5 images far larger than shown
77 KiB5 images are downloaded at several times the size a phone draws them, for example 004.png at 616 px wide, shown at 184 px. Resized copies would save about 77 KiB.
About 3.7 g of CO₂ per visit
3.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.73 g of CO₂e: 447.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
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (10 elements)
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 10 elements on the page fail this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (12 elements)
Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 5 failed. 5 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
26 links crawlers can't follow
26 links have no real href, so search engines can't follow them.
Meta description is long (347 characters)
Your meta description is 347 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
176 internal links, 36 external
The homepage links to 176 pages on rejuvenation.com and 36 external pages.
4 checks passed
Title: 57 characters
Your title is a healthy 57 characters: “Heirloom-Quality Lighting, Hardware & More | Rejuvenation”.
Canonical URL set
The canonical URL is https://www.rejuvenation.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://www.rejuvenation.com/netstorage/sitemaps/ecm-sitemap-index.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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 (685 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.rejuvenation.com/llms.txt (12 KiB, 38 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.rejuvenation.com/ccvalueprop, which answers with an error. Visitors hit a dead end and search engines drop it.
3 pages without a meta description
https://www.rejuvenation.com/customer-service/privacy, https://www.rejuvenation.com/pages/gift-cards.html and https://www.rejuvenation.com/customer-service have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.rejuvenation.com/customer-service/privacy, https://www.rejuvenation.com/pages/gift-cards.html and https://www.rejuvenation.com/customer-service 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 81 found) and read each the way a search engine does.
4 checks passed
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 5 pages that loaded have a <title>.
Best practices
10 small tap targets
10 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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 “Hydration completed but contains mismatches.”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
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 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 544 words of copy
The homepage carries about 544 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “contact us” and “SIGN UP”.
17 calls to action
The homepage has 17 calls to action, for example “Learn More”, “Track Order” and “Call Us 1.888.401.1900”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Tag Manager, Meta Pixel, Microsoft Ads and Pinterest Tag (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.
49 cookies set on arrival
49Opening the homepage sets 49 cookies, 3 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.
31 other companies contacted
Loading the homepage contacts 31 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 rejuvenation.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Hosting
- Akamai
Company
- Founded
- 1977
- Headquarters
- Portland
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on rejuvenation.com, including 29 speed issues, 6 SEO 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.