Website review, no card needed
durobumps.com website review
Visit site (opens in a new tab)Reviewed 8 November 202642 issues · 92 checks
This review found 42 issues worth fixing on durobumps.com, 17 of them high impact, across 92 checks. The most urgent: page weight: 9.1 MB in 293 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
84B- #21,263 of 118,015 reviewed websitesbeats 77%
- #13,831 of 67,064 online storesbeats 73%
- #13,426 of 61,148 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 71 ms |
| May 23, 2026 | 75 ms |
| May 30, 2026 | 77 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 74 ms |
| Jun 20, 2026 | 70 ms |
| Jun 27, 2026 | 71 ms |
| Jul 4, 2026 | 78 ms |
| Jul 11, 2026 | 75 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 75 ms |
| Aug 1, 2026 | 71 ms |
| Aug 8, 2026 | 72 ms |
| Aug 15, 2026 | 74 ms |
| Aug 22, 2026 | 78 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 80 ms |
| Sep 12, 2026 | 81 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 84 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 80 ms |
| Oct 24, 2026 | 72 ms |
| Oct 31, 2026 | 75 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
Speed
4,864 HTML elements
The page has 4,864 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
822 KiB6 images could be 822 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
500 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Shopify adds 69 ms
69 msShopify costs a phone 69 ms of main-thread work and 434 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.
8 third-party services on the page
8 third-party services load with your homepage (Hubspot, Google CDN and Shopify and others), adding 699 KiB and 283 ms of main-thread time.
Use efficient cache lifetimes
118 KiB19 files are served with short cache lifetimes, so returning visitors download them again (118 KiB).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 104 ms. During a long task the page ignores taps.
Reduce unused JavaScript
62 KiBAbout 62 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
37 KiBAbout 37 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
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 JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 743 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SMOOTHER RIDE - PROTECT YOUR SUSPENSION PROUDLY MADE IN THE…”.
Time to Interactive: 18.7 s
18.7 sThe page becomes fully interactive after 18.7 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.
43 images without width and height
43 images have no width and height attributes, so the layout jumps as each one loads.
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 71 ms to 75 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 77 ms
77 msReal visitors wait 77 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.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 421 ms
421 msReal visitors wait 421 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 31 ms
31 msScripts block the page for only 31 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.1 MB in 293 requests
9.1 MBYour homepage downloads 9.1 MB in 293 requests on a phone: media 3.7 MB (2), images 3.6 MB (42) and other files 873 KiB (133). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.
12 images far larger than shown
2.2 MB12 images are downloaded at several times the size a phone draws them, for example durobumps-launches-jeep-wrangler-jk-jl-and-jeep-gladiator-jt at 1,251 px wide, shown at 340 px. Resized copies would save about 2.2 MB.
19 images in older formats
19 images (8.2 MB) 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.
15 images below the first screen load straight away
15 images further down the page (6.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.57 g of CO₂e: 308.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (3 elements)
ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (3 elements)
Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
50 images without alt text
50 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
17 links without text
17 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.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 11 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“DuroBumps” and “smoother ride - protect your suspension proudly m…”). One clear main headline is easier for people and search engines.
Structured data has 3 problems
Structured data found (Organization and WebSite) but with 3 problems, for example “Organization: sameAs is not an absolute URL ("Facebook.com/durobump")”.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
177 internal links, 2 external
The homepage links to 177 pages on durobumps.com and 2 external pages.
6 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “DuroBumps Bump Stops provide smooth, progressive dampening for Toyota 4Runner, Tacoma, Tundra, Land Cruisers, FJ Cruise…”.
Title: 42 characters
Your title is a healthy 42 characters: “DuroBumps Premium Off Road Road Bump Stops”.
Canonical URL set
The canonical URL is https://durobumps.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://durobumps.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (2,973 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://durobumps.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://durobumps.com/instagram.com/durobumps and https://durobumps.com/YouTube.com/@durobumps, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page without a title
https://durobumps.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://durobumps.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://durobumps.com/Facebook.com/durobump and https://durobumps.com/blogs/event all use the title “Event – DuroBumps”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages without a meta description
https://durobumps.com/collections/fox-hydraulic-bump-stops, https://durobumps.com/collections/king-air-bump, https://durobumps.com/blogs/news, https://durobumps.com/customer_authentication/redirect, https://durobumps.com/Facebook.com/durobump and https://durobumps.com/pages/become-a-duro-bumps-dealer and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://durobumps.com/Facebook.com/durobump, whose canonical is https://durobumps.com/blogs/event. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages without an H1
https://durobumps.com/collections/fox-hydraulic-bump-stops, https://durobumps.com/collections/king-air-bump, https://durobumps.com/blogs/news, https://durobumps.com/customer_authentication/redirect, https://durobumps.com/Facebook.com/durobump and https://durobumps.com/pages/become-a-duro-bumps-dealer and 7 others 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 71 found) and read each the way a search engine does.
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
19 of 22 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address 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: 16 testimonial or review blocks. 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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,504 words of copy
The homepage carries about 1,504 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
18 calls to action
The homepage has 18 calls to action, for example “Contact”, “CALL US (480) 448-9848” and “Contact Us”.
5 short forms
5 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.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (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.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 6 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 durobumps.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blotout Edgetag · Judge Me Reviews · Mw Bundle Builder · chimpstatic.com · hubapi.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
- jQuery
- 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 42 issues on durobumps.com, 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.