Website review, no card needed
reynoldsonline.com website review
Visit site (opens in a new tab)Reviewed 20 November 202638 issues · 69 checks
This review found 38 issues worth fixing on reynoldsonline.com, 16 of them high impact, across 69 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.7 s |
| Oct 31, 2026 | 3.7 s |
| Nov 7, 2026 | 3.8 s |
| Nov 14, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 798 ms |
| Jun 6, 2026 | 636 ms |
| Jun 13, 2026 | 562 ms |
| Jun 20, 2026 | 543 ms |
| Jun 27, 2026 | 573 ms |
| Jul 4, 2026 | 573 ms |
| Jul 11, 2026 | 634 ms |
| Jul 18, 2026 | 660 ms |
| Jul 25, 2026 | 634 ms |
| Aug 1, 2026 | 638 ms |
| Aug 8, 2026 | 617 ms |
| Aug 15, 2026 | 509 ms |
| Aug 22, 2026 | 363 ms |
| Aug 29, 2026 | 286 ms |
| Sep 5, 2026 | 194 ms |
| Sep 12, 2026 | 181 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 182 ms |
| Oct 10, 2026 | 177 ms |
| Oct 17, 2026 | 179 ms |
| Oct 24, 2026 | 169 ms |
| Oct 31, 2026 | 166 ms |
| Nov 7, 2026 | 159 ms |
| Nov 14, 2026 | 154 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.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.0 s
3.5 s
Speed
Reduce unused JavaScript
2.7 s · 532 KiBAbout 532 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Cookiebot and EpiServer and others), adding 1.1 MB and 339 ms of main-thread time.
Improve image delivery
350 ms · 67 KiB3 images could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 386 ms. During a long task the page ignores taps.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 238 ms
238 msGoogle Tag Manager costs a phone 238 ms of main-thread work and 336 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.
1,798 HTML elements
The page has 1,798 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Cloudinary adds 0 ms
0 msCloudinary costs a phone 0 ms of main-thread work and 603 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.
Use efficient cache lifetimes
150 ms · 39 KiB2 files are served with short cache lifetimes, so returning visitors download them again (39 KiB).
Reduce unused CSS
46 KiBAbout 46 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 24 ms
24 msYour server sent the HTML in 24 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.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.85
0.85For real visitors the layout shifts by 0.85 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 13.6 s
13.6 sYour largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LIGHTING DESIGNS AND MATERIALS TO TRANSFORM YOUR PROJECT LE…”.
Time to Interactive: 13.6 s
13.6 sThe page becomes fully interactive after 13.6 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 934 ms
934 msReal visitors wait 934 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 179 ms
179 msReal visitors wait 179 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 78% faster for real visitors
-78%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 798 ms to 154 ms 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: 2.2 MB in 40 requests
2.2 MBYour homepage downloads 2.2 MB in 40 requests on a phone: scripts 1.1 MB (8), images 603 KiB (13) and other files 366 KiB (15). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
Alternative text of images should not be repeated as text (7 elements)
Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
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.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 checks passed
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.reynoldsonline.com/sitemapindex.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 419 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
2 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.
llms.txt published
The site publishes https://www.reynoldsonline.com/llms.txt (11 KiB, 0 links), a plain-text guide to the site for AI tools.
Best practices
9 small tap targets
9 of 34 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
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 419 words of copy
The homepage carries about 419 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
Analytics in place
Analytics detected: Google Tag Manager.
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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 reynoldsonline.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on reynoldsonline.com, including 20 speed issues, 8 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.