Website review, no card needed
finolexpipes.com website review
Visit site (opens in a new tab)Reviewed 26 October 202644 issues · 92 checks
This review found 44 issues worth fixing on finolexpipes.com, 12 of them high impact, across 92 checks. The most urgent: page weight: 60.3 MB in 97 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.5 s |
| May 16, 2026 | 5.5 s |
| May 23, 2026 | 5.5 s |
| May 30, 2026 | 5.6 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 357 ms |
| May 16, 2026 | 355 ms |
| May 23, 2026 | 355 ms |
| May 30, 2026 | 347 ms |
| Jun 6, 2026 | 205 ms |
| Jun 13, 2026 | 195 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 199 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 202 ms |
| Jul 18, 2026 | 204 ms |
| Jul 25, 2026 | 200 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 193 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 185 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 185 ms |
| Sep 26, 2026 | 184 ms |
| Oct 3, 2026 | 185 ms |
| Oct 10, 2026 | 185 ms |
| Oct 17, 2026 | 184 ms |
| Oct 24, 2026 | 189 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
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.7 s
7.8 s
8.9 s
Speed
Reduce unused JavaScript
2.3 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
2.0 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.1 MB and 1.0 s of main-thread time.
Mobile performance score: 59
59/100Your mobile performance score is 59 (desktop: 60). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 435 KiB7 images could be 435 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Google CDN adds 420 ms
420 msGoogle CDN costs a phone 420 ms of main-thread work and 1.1 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.
Google Tag Manager adds 336 ms
336 msGoogle Tag Manager costs a phone 336 ms of main-thread work and 632 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.
Use efficient cache lifetimes
338 KiB9 files are served with short cache lifetimes, so returning visitors download them again (338 KiB).
Reduce unused CSS
300 ms · 26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Facebook adds 181 ms
181 msFacebook costs a phone 181 ms of main-thread work and 306 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 137 ms. During a long task the page ignores taps.
Legacy JavaScript
54 KiBPolyfills for old browsers add 54 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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 213 ms
213 msYour server sent the HTML in 213 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.
Speed Index: 14.6 s
14.6 sVisually, the page fills in at 14.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Finolex Pipes logo”.
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 291 ms
291 msReal visitors wait 291 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
85 images without width and height
85 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 48% faster for real visitors
-48%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 357 ms to 189 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 51% faster for real visitors
-51%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 154 ms
154 msScripts block the page for only 154 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 60.3 MB in 97 requests
60.3 MBYour homepage downloads 60.3 MB in 97 requests on a phone: media 53.3 MB (8), images 4.3 MB (36) and scripts 2.1 MB (23). Under 2 MB keeps phones on slow connections fast.
7 images below the first screen load straight away
7 images further down the page (550 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
65 KiB1 image is downloaded at several times the size a phone draws it, for example Logo_transparent_footer.png at 5,061 px wide, shown at 160 px. Resized copies would save about 65 KiB.
1 image in older formats
1 image (66 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 17.1 g of CO₂ per visit
17.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 17.10 g of CO₂e: 2052.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (2 elements)
Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (43 elements)
All page content should be contained by landmarks: 43 elements on the page fail this check, rated moderate by axe-core.
18 form fields without a label
18 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 61 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 12 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “PVC Pipes & Fittings - Leading PVC Pipe Manufacturer | Finolex Pipes”.
7 links crawlers can't follow
7 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.
92 internal links, 9 external
The homepage links to 92 pages on finolexpipes.com and 9 external pages.
7 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Explore high-quality PVC pipes and fittings from Finolex, a leading manufacturer. Find durable, reliable solutions for …”.
One H1 headline
Your main headline reads: “Finolex Pipes & Fittings | PVC Pipe Manufacturers”.
Canonical URL set
The canonical URL is https://www.finolexpipes.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.finolexpipes.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,337 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.finolexpipes.com/llms.txt (89 KiB, 3 links), a plain-text guide to the site for AI tools.
Other pages
9 pages slow to respond
https://www.finolexpipes.com/agriculture-products/agriculture-pipes-fittings, https://www.finolexpipes.com/agriculture-products/column-pipes, https://www.finolexpipes.com/agriculture-products/solvent-cement-lubricants-agri-products, https://www.finolexpipes.com/plumbing-products, https://www.finolexpipes.com/plumbing-products/swr-pipes-fittings and https://www.finolexpipes.com/plumbing-products/sewerage-pipes and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
24 of 27 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 35 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
A 9-field form
Your longest form asks for 9 fields (1 required). Every extra field lowers completion.
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,503 words of copy
The homepage carries about 1,503 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” and “Interested to join the Finolex Parivar”.
6 calls to action
The homepage has 6 calls to action, for example “Investor Relations Contact Details”, “Contact Us” and “Interested to join the Finolex Parivar”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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 (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.
17 other companies contacted
Loading the homepage contacts 17 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 finolexpipes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on finolexpipes.com, including 21 speed issues, 3 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.