Website review, no card needed
521restorations.com website review
Visit site (opens in a new tab)Reviewed 1 November 202642 issues · 95 checks
This review found 42 issues worth fixing on 521restorations.com, 10 of them high impact, across 95 checks. The most urgent: 16,027 HTML elements. 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
74C- #56,387 of 81,503 reviewed websitesbeats 27%
- #31,370 of 40,351 online storesbeats 18%
- #443 of 716 BigCommerce storesbeats 33%
Closest competitors among BigCommerce stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
521restorations.com does not allow embedding, so this is Google's rendering of the page.
Speed
16,027 HTML elements
The page has 16,027 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
1.1 s · 490 KiB20 images could be 490 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 93 KiBAbout 93 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Render-blocking requests
550 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused JavaScript
450 ms · 89 KiBAbout 89 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Bigcommerce and Google Fonts), adding 1.1 MB and 333 ms of main-thread time.
Bigcommerce adds 333 ms
333 msBigcommerce costs a phone 333 ms of main-thread work and 1.0 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.
Use efficient cache lifetimes
300 ms · 103 KiB4 files are served with short cache lifetimes, so returning visitors download them again (103 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 198 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 5 KiB5 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 388 ms of it running JavaScript. That is comfortably low.
Server response: 61 ms
61 msYour server sent the HTML in 61 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Filler neck for 72-77 Dodge Trucks with in cab tank. Replac…”.
Time to Interactive: 5.9 s
5.9 sThe page becomes fully interactive after 5.9 s. Good is under 3.8 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 203 ms
203 msScripts block taps and scrolling for 203 ms in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Speed Index: 2.5 s
2.5 sVisually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
1 image in older formats
1 image (86 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 0.4 g of CO₂ per visit
0.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 43.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.3 MB in 43 requests
1.3 MBYour homepage downloads 1.3 MB in 43 requests on a phone: images 831 KiB (28), scripts 192 KiB (6) and stylesheets 105 KiB (2). That is a lean page.
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
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (39 elements)
All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 66 images in the HTML carry an alt attribute.
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 8 failed. 2 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.
Title is short (16 characters)
Your title is only 16 characters: “521 Restorations”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (7 characters)
Your meta description is only 7 characters: “1382224”. 70 to 160 characters is enough to sell the click.
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.
No XML sitemap
No XML sitemap at https://521restorations.com/sitemap.xml, so Google discovers your pages only by following links.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
4,642 internal links, 2 external
The homepage links to 4,642 pages on 521restorations.com and 2 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://521restorations.com/.
robots.txt in place
robots.txt is in place.
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.
No llms.txt
There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Text is in the HTML
Your server sends the page's text in the HTML (10,189 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
/all_models, /all_models/airgrabber-ramcharger, /all_models/airgrabber-ramcharger/fasteners, /all_models/airgrabber-ramcharger/seals, /all_models/brake and /all_models/brake/brake-brackets and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
/all_models, /all_models/airgrabber-ramcharger, /all_models/airgrabber-ramcharger/fasteners, /all_models/airgrabber-ramcharger/seals, /all_models/brake and /all_models/brake/brake-brackets and 8 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 196 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
43 small tap targets
43 of 119 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “fbq is not defined”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
Short HSTS lifetime
HSTS is set, but max-age is 0 days; one year is the recommended minimum.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
6 checks passed
Served over HTTPS
The homepage is served over HTTPS (521restorations.com).
Valid certificate (53 days left)
The certificate from Google Trust Services · WE1 verifies for 521restorations.com and is valid for another 53 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
http:// redirects to https
http://521restorations.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 41 links work
All 41 links checked from your homepage (40 internal, 1 external) answered without errors.
Domain and trust
Domain expires in 21 days
521restorations.com is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.
No CAA record
521restorations.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
521restorations.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
1 checks passed
Domain is 19 years old
19 years521restorations.com was registered in Nov 2006 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.
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.
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 494 words of copy
The homepage carries about 494 words of visible text.
2 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Sign Up” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be 521restorations.com is still delivered. Add a report address, check the reports, then move to quarantine.
No DKIM key on the usual selectors
We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.
Email authentication score: 65/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
1 checks passed
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 +a +mx include:_spf.bigcommerce.com include:_spf.521restorations.com -all”.
Privacy and tracking
12 cookies set on arrival
12Opening the homepage sets 12 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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Upkeep, stack and company
Stack
- E-commerce
- BigCommerce
- Hosting
- Bigcommerce
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 521restorations.com, including 13 speed issues, 7 SEO issues and 4 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.