Website review, no card needed

finolex.com logo

finolex.com website review

Visit site (opens in a new tab)Reviewed 19 November 202617 issues · 52 checks

This review found 17 issues worth fixing on finolex.com, 6 of them high impact, across 52 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
4.1 s3.3 sMay 30Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.6 s
Jul 11, 20263.5 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.6 s
Aug 15, 20263.9 s
Aug 22, 20263.9 s
Aug 29, 20264.0 s
Sep 5, 20263.9 s
Sep 12, 20263.6 s
Sep 19, 20263.6 s
Sep 26, 20263.5 s
Oct 3, 20263.6 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.6 s
Oct 31, 20263.6 s
Nov 7, 20263.4 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
165 ms132 msMay 30Nov 14160 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026146 ms
Jun 6, 2026146 ms
Jun 13, 2026139 ms
Jun 20, 2026137 ms
Jun 27, 2026136 ms
Jul 4, 2026137 ms
Jul 11, 2026136 ms
Jul 18, 2026139 ms
Jul 25, 2026139 ms
Aug 1, 2026142 ms
Aug 8, 2026156 ms
Aug 15, 2026159 ms
Aug 22, 2026160 ms
Aug 29, 2026161 ms
Sep 5, 2026161 ms
Sep 12, 2026160 ms
Sep 19, 2026158 ms
Sep 26, 2026156 ms
Oct 3, 2026144 ms
Oct 10, 2026139 ms
Oct 17, 2026136 ms
Oct 24, 2026137 ms
Oct 31, 2026145 ms
Nov 7, 2026160 ms
Nov 14, 2026160 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

4 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user FCP: 3.2 s

    3.2 s

    Real visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Real-user LCP: 3.4 s

    3.4 s

    Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 146 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user INP: 159 ms

    159 ms

    Real visitors wait 159 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

Images and page weight

100
  • About 0.01 g of CO₂ per visit

    0.01 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.01 g of CO₂e: 0.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Page weight: 24 KiB

    24 KiB

    Your homepage downloads 24 KiB on a phone. That is a lean page.

Accessibility

3 to fix75
  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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.

  • Headings skip levels

    Headings skip levels (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 5 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fix73
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (168 characters)

    Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 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 favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 167 internal links, 6 external

    The homepage links to 167 pages on finolex.com and 6 external pages.

3 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “Welcome to Finolex Cables | Finolex Cables.”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://finolex.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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 https://finolex.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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

1 to fix95
  • 2 pages without an H1

    https://finolex.com/View/Page/History and https://finolex.com/View/Page/Awards have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://finolex.com/View/Page/History and https://finolex.com/View/Page/Awards took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 121 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    4 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.

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

  • 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 4 pages that loaded have a <title>.

Best practices

100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 542 words of copy

    The homepage carries about 542 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Analyst meeting schedule”, “Contact Details” and “Media Kit Download”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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).

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 finolex.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
jQuery
Analytics
Google Tag Manager

Company

Founded
1958
Headquarters
Pune

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 17 issues on finolex.com, including 4 speed issues, 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25