Website review, no card needed
fiberoncladding.com website review
Visit site (opens in a new tab)Reviewed 9 November 202635 issues · 95 checks
This review found 35 issues worth fixing on fiberoncladding.com, 8 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. 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
One 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
fiberoncladding.com does not allow embedding, so this is Google's rendering of the page.
Speed
Use efficient cache lifetimes
2.5 s · 392 KiB15 files are served with short cache lifetimes, so returning visitors download them again (392 KiB).
Reduce unused JavaScript
1.2 s · 325 KiBAbout 325 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.0 MB and 926 ms of main-thread time.
Improve image delivery
400 ms · 602 KiB14 images could be 602 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 343 ms
343 msGoogle Tag Manager costs a phone 343 ms of main-thread work and 472 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 · 41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
300 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 198 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.
1 checks passed
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: 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 image.
Time to Interactive: 13.8 s
13.8 sThe page becomes fully interactive after 13.8 s. Good is under 3.8 s.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 313 ms
313 msScripts block taps and scrolling for 313 ms in total while the page loads. Good is under 200 ms.
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.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Cumulative Layout Shift: 0.042
0.042The layout barely moves while loading (CLS 0.042, good is under 0.1).
Images and page weight
Page weight: 3.0 MB in 184 requests
3.0 MBYour homepage downloads 3.0 MB in 184 requests on a phone: scripts 1.2 MB (56), images 1,007 KiB (21) and other files 692 KiB (97). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BST_Clad_WLD_Eden_Tupelo_002_500x.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).
1 image below the first screen load straight away
1 image further down the page (34 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 101.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
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.
ARIA role should be appropriate for the element (12 elements)
ARIA role should be appropriate for the element: 12 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 32 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 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 (26 characters)
Your title is only 26 characters: “Fiberon Composite Cladding”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (203 characters)
Your meta description is 203 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
110 internal links, 7 external
The homepage links to 110 pages on fiberoncladding.com and 7 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.fiberoncladding.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://www.fiberoncladding.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (521 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to /pages/composite-decking, which answers with an error. Visitors hit a dead end and search engines drop it.
10 pages without a meta description
/pages/where-to-buy, /pages/ceu-eligible-courses, /pages/architect-assistance, /pages/about-fiberon, /pages/fiberon-balance and /blogs/news and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
/pages/where-to-buy, /pages/faq, /pages/ceu-eligible-courses, /pages/architect-assistance, /pages/contact and /pages/about-fiberon and 5 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 37 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 14 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
19 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
1 broken link to your own pages
1 link from your homepage to your own site is broken, for example https://www.fiberoncladding.com/pages/composite-decking (404).
Short HSTS lifetime
HSTS is set, but max-age is 91 days; one year is the recommended minimum.
1 link through redirect chains
1 link go through two or more redirects, for example https://www.fiberoncladding.com/account.
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.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
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 (fiberoncladding.com).
Valid certificate (58 days left)
The certificate from Let's Encrypt · YE2 verifies for fiberoncladding.com and is valid for another 58 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
http:// redirects to https
http://fiberoncladding.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.
Domain and trust
Domain expires in 36 days
fiberoncladding.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.
DNSSEC is off
fiberoncladding.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.
2 checks passed
Domain is 9 years old
9 yearsfiberoncladding.com was registered in Dec 2016 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.
Certificate issuers are restricted
CAA records allow only digicert.com, globalsign.com, letsencrypt.org and pki.goog to issue certificates for fiberoncladding.com, so a mis-issued certificate from anyone else is refused.
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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 298 words of copy
The homepage carries about 298 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: “ORDER SAMPLES”.
12 calls to action
The homepage has 12 calls to action, for example “Where to Buy”, “Contact Us” and “Learn more”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and HubSpot.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be fiberoncladding.com is still delivered. Reports are on, so moving to quarantine is the next step.
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: 60/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 in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 ip4:205.220.181.251 ip4:205.220.170.192 ip4:148.163.143.46 ip4:148.163.147.97 mx:fiberoncladding.com ~all”.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
24 cookies set on arrival
24Opening the homepage sets 24 cookies, 7 of them by other companies (measured from a US location before any click).
36 other companies contacted
Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
Apps on your store
No apps were seen in the code your storefront loads.
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
- It loads jQuery 1.10.2, older than 3.5 (which fixed known security holes).
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on fiberoncladding.com, including 15 speed issues, 5 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.