Website review, no card needed
riversedgeproducts.com website review
Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 72 checks
This review found 26 issues worth fixing on riversedgeproducts.com, 9 of them high impact, across 72 checks. The most urgent: improve image delivery. 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
85B- #16,247 of 120,200 reviewed websitesbeats 82%
- #10,300 of 68,092 online storesbeats 79%
- #10,006 of 62,056 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 96 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 102 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 108 ms |
| Aug 8, 2026 | 108 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 118 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 113 ms |
| Oct 31, 2026 | 110 ms |
| Nov 7, 2026 | 105 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
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.6 s
4.2 s
Speed
Improve image delivery
2.5 s · 1.8 MB27 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Reduce unused JavaScript
1.8 s · 485 KiBAbout 485 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Shopify adds 141 ms
141 msShopify costs a phone 141 ms of main-thread work and 661 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,726 HTML elements
The page has 1,726 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and UniConsent CMP and others), adding 887 KiB and 280 ms of main-thread time.
Reduce unused CSS
150 ms · 55 KiBAbout 55 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.
Use efficient cache lifetimes
150 ms · 23 KiB10 files are served with short cache lifetimes, so returning visitors download them again (23 KiB).
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 619 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 30.1 s
30.1 sYour largest element takes 30.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 30.5 s
30.5 sThe page becomes fully interactive after 30.5 s. Good is under 3.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 96 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 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).
Total Blocking Time: 29 ms
29 msScripts block the page for only 29 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.3 MB in 222 requests
6.3 MBYour homepage downloads 6.3 MB in 222 requests on a phone: images 4.4 MB (29), scripts 959 KiB (89) and other files 766 KiB (93). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Longer_Nights_Warmer_Lights_Lantern_Display.png 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 in older formats
1 image (471 KiB) is 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.8 g of CO₂ per visit
1.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.78 g of CO₂e: 213.1 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
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (91 characters)
Your title is 91 characters, so Google will cut it off around 60: “River’s Edge Products | Rustic Decor & Gifts for Outdoor Enthusiasts – Rivers Edge Produc…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
274 internal links, 28 external
The homepage links to 274 pages on riversedgeproducts.com and 28 external pages.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Explore River’s Edge Products for rustic, western, and nautical decor that brings the outdoors into your home. Perfect …”.
One H1 headline
Your main headline reads: “Rivers Edge Products”.
Canonical URL set
The canonical URL is https://riversedgeproducts.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://riversedgeproducts.com/sitemap.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 (716 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://riversedgeproducts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://riversedgeproducts.com/collections/gibson-rep-lighters has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://riversedgeproducts.com/collections/gibson-rep-lighters 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 127 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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
29 of 32 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 219 words
The homepage has only about 219 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.
2 checks passed
8 calls to action
The homepage has 8 calls to action, for example “SHOP ALL”, “Shop All” and “DOWNLOAD PDF HERE”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
37 other companies contacted
Loading the homepage contacts 37 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 riversedgeproducts.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Az Google Font Custom Fonts · Judge Me Reviews · Hulk Form Builder · Goalify Free Shipping Goals · Klaviyo Email Marketing Sms · Forms · Collection Cart · Moast · ywxi.net · buynowbutton.us · recovermycart.com · cloudfront.net · trustedsite.com · uniconsent.com · getredo.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
- Bootstrap
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Franklin
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on riversedgeproducts.com, including 10 speed issues, 2 SEO issues and 5 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.