Website review, no card needed
fastrackpolyfab.com website review
Visit site (opens in a new tab)Reviewed 6 November 202655 issues · 85 checks
This review found 55 issues worth fixing on fastrackpolyfab.com, 24 of them high impact, across 85 checks. The most urgent: render-blocking 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
52FClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.3 s
4.1 s
4.9 s
5.7 s
6.5 s
Speed
Render-blocking requests
6.8 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.8 s.
Reduce unused CSS
5.3 s · 910 KiBAbout 910 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Reduce unused JavaScript
4.8 s · 811 KiBAbout 811 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
850 ms · 7.9 MB16 files are served with short cache lifetimes, so returning visitors download them again (7.9 MB).
Improve image delivery
150 ms · 8.2 MB16 images could be 8.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Font display
950 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 950 ms).
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Google Tag Manager and GitHub and others), adding 1.3 MB and 484 ms of main-thread time.
YouTube adds 349 ms
349 msYouTube costs a phone 349 ms of main-thread work and 988 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.
Minify CSS
300 ms · 45 KiB45 KiB could be saved by minifying CSS.
Minify JavaScript
150 ms · 25 KiB25 KiB could be saved by minifying JavaScript.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 143 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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 632 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 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 CLS: 0.70
0.70For real visitors the layout shifts by 0.70 (75th percentile). Good is under 0.1.
First Contentful Paint: 7.8 s
7.8 sThe first text or image appears after 7.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 33.5 s
33.5 sYour largest element takes 33.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 34.9 s
34.9 sThe page becomes fully interactive after 34.9 s. Good is under 3.8 s.
Speed Index: 14.3 s
14.3 sVisually, the page fills in at 14.3 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.982
0.982The layout shifts by 0.982 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
1 checks passed
Total Blocking Time: 122 ms
122 msScripts block the page for only 122 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 12.7 MB in 89 requests
12.7 MBYour homepage downloads 12.7 MB in 89 requests on a phone: images 10.1 MB (24), scripts 1.5 MB (29) and stylesheets 918 KiB (20). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 6.9 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
6.5 MB9 images are downloaded at several times the size a phone draws them, for example weship2.webp at 1,080 px wide, shown at 150 px. Resized copies would save about 6.5 MB.
9 images below the first screen load straight away
9 images further down the page (7.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images in older formats
6 images (670 KiB) 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.
About 3.6 g of CO₂ per visit
3.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.61 g of CO₂e: 432.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 buttons without a name
13 buttons have no accessible name, so screen readers announce just “button”.
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
37 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: 37 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
Title is short (23 characters)
Your title is only 23 characters: “Fastrack Polyfab – Home”. 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.
27 links with vague text
27 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
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://fastrackpolyfab.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at fastrackpolyfab.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
33 internal links, 11 external
The homepage links to 33 pages on fastrackpolyfab.com and 11 external pages.
1 checks passed
Canonical URL set
The canonical URL is https://fastrackpolyfab.com/index.htm.
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.
Some text only appears after JavaScript runs
54%The HTML your server sends has 1,201 of the 2,238 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://fastrackpolyfab.com/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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
11 pages without a title
https://fastrackpolyfab.com/products/productdetailpage/HDPEROLLS/PLATINUMPEROLLSERIES/Platinumgold.html, https://fastrackpolyfab.com/products/productdetailpage/HDPEROLLS/SERIES/karatpremium.html, https://fastrackpolyfab.com/products/productdetailpage/HDPETARPAULIN/PLATINUMSERIES/Platinumgold.html, https://fastrackpolyfab.com/products/productdetailpage/GEOMEMBRANE/PlatinumBlack.html, https://fastrackpolyfab.com/products/productdetailpage/HDPELUMBERWRAP/HDPELUMBERWRAP.html and https://fastrackpolyfab.com/products/productdetailpage/TRUCKCOVER/truck.html and 5 others have no <title>, so Google invents the link text in results.
15 pages without a meta description
https://fastrackpolyfab.com/aboutus/about.htm, https://fastrackpolyfab.com/products/products.htm, https://fastrackpolyfab.com/exhibition/exhibition.htm, https://fastrackpolyfab.com/contact/contactus.htm, https://fastrackpolyfab.com/products/productdetailpage/HDPEROLLS/PLATINUMPEROLLSERIES/Platinumgold.html and https://fastrackpolyfab.com/products/productdetailpage/HDPEROLLS/SERIES/karatpremium.html and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://fastrackpolyfab.com/aboutus/about.htm, whose canonical is https://fastrackpolyfab.com/aboutus/index.htm. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://fastrackpolyfab.com/aboutus/about.htm, https://fastrackpolyfab.com/products/products.htm, https://fastrackpolyfab.com/exhibition/exhibition.htm, https://fastrackpolyfab.com/contact/contactus.htm, https://fastrackpolyfab.com/products/productdetailpage/HDPEROLLS/PLATINUMPEROLLSERIES/Platinumgold.html and https://fastrackpolyfab.com/products/productdetailpage/HDPEROLLS/SERIES/karatpremium.html and 9 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 17 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
Best practices
10 broken images
10 images failed to load on a phone, for example https://fastrackpolyfab.com/wp-content/uploads/2017/01/pic3-768x397.jpg.
52 small tap targets
52 of 75 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 2,238 words of copy
The homepage carries about 2,238 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
2 calls to action
The homepage has 2 calls to action, for example “Contact Us”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 4 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 1 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.
13 other companies contacted
Loading the homepage contacts 13 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 fastrackpolyfab.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 55 issues on fastrackpolyfab.com, including 20 speed issues, 8 SEO issues and 1 conversion gap. 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.