Website review, no card needed

a1fenceproducts.com logo

a1fenceproducts.com website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 91 checks

This review found 36 issues worth fixing on a1fenceproducts.com, 9 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
6.1 s3.0 sMay 16Oct 313.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.5 s
May 23, 20265.6 s
May 30, 20265.7 s
Jun 6, 20265.6 s
Jun 13, 20265.2 s
Jun 20, 20264.5 s
Jun 27, 20264.4 s
Jul 4, 20264.2 s
Jul 11, 20263.8 s
Jul 18, 20263.8 s
Jul 25, 20263.7 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20263.7 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.9 s
Sep 12, 20263.8 s
Sep 19, 20263.7 s
Sep 26, 20263.7 s
Oct 3, 20263.7 s
Oct 10, 20263.6 s
Oct 17, 20263.4 s
Oct 24, 20263.3 s
Oct 31, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
257 ms102 msMay 16Oct 31122 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026239 ms
May 23, 2026231 ms
May 30, 2026216 ms
Jun 6, 2026196 ms
Jun 13, 2026157 ms
Jun 20, 2026132 ms
Jun 27, 2026131 ms
Jul 4, 2026129 ms
Jul 11, 2026126 ms
Jul 18, 2026122 ms
Jul 25, 2026125 ms
Aug 1, 2026128 ms
Aug 8, 2026128 ms
Aug 15, 2026127 ms
Aug 22, 2026128 ms
Aug 29, 2026126 ms
Sep 5, 2026127 ms
Sep 12, 2026126 ms
Sep 19, 2026120 ms
Sep 26, 2026121 ms
Oct 3, 2026123 ms
Oct 10, 2026125 ms
Oct 17, 2026126 ms
Oct 24, 2026124 ms
Oct 31, 2026122 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

Full-page screenshot of a1fenceproducts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. a1fenceproducts.com at 0.4 s0.4 s
  2. a1fenceproducts.com at 0.8 s0.8 s
  3. a1fenceproducts.com at 1.1 s1.1 s
  4. a1fenceproducts.com at 1.5 s1.5 s
  5. a1fenceproducts.com at 1.9 s1.9 s
  6. a1fenceproducts.com at 2.3 s2.3 s
  7. a1fenceproducts.com at 2.6 s2.6 s
  8. a1fenceproducts.com at 3.0 s3.0 s

Speed

11 to fix56
  • Reduce unused JavaScript

    2.9 s · 962 KiB

    About 962 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Render-blocking requests

    1.7 s

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.

  • Improve image delivery

    50 ms · 1.8 MB

    32 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Hotjar and others), adding 2.0 MB and 1.2 s of main-thread time.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • Font display

    600 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).

  • Google Tag Manager adds 488 ms

    488 ms

    Google Tag Manager costs a phone 488 ms of main-thread work and 804 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.

  • Google CDN adds 399 ms

    399 ms

    Google CDN costs a phone 399 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.

  • Reduce unused CSS

    450 ms · 38 KiB

    About 38 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Main-thread work: 3.3 s

    A phone's processor spends 3.3 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1,528 HTML elements

    The page has 1,528 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 15 long tasks on the main thread

    15 long tasks block the main thread while loading, the longest for 183 ms. During a long task the page ignores taps.

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    35 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (35 KiB).

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 99 ms

    99 ms

    Your server sent the HTML in 99 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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.

  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your largest element takes 9.4 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: 19.8 s

    19.8 s

    The page becomes fully interactive after 19.8 s. Good is under 3.8 s.

  • Speed Index: 5.8 s

    5.8 s

    Visually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Total Blocking Time: 474 ms

    474 ms

    Scripts block taps and scrolling for 474 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

5 checks passed
  • Real-user INP: 126 ms

    126 ms

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (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-31, real Chrome visitors' tap response (inp) went from 239 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 39% faster for real visitors

    -39%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix50
  • Page weight: 5.7 MB in 147 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 147 requests on a phone: images 2.9 MB (73), scripts 2.0 MB (36) and other files 357 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 12 images in older formats

    12 images (1.3 MB) 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.

  • 1 image far larger than shown

    42 KiB

    1 image is downloaded at several times the size a phone draws it, for example slider-2.webp at 1,300 px wide, shown at 360 px. Resized copies would save about 42 KiB.

  • About 1.6 g of CO₂ per visit

    1.61 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 7489
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

    3 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 (42 elements)

    All page content should be contained by landmarks: 42 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.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 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), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 64 images in the HTML carry an alt attribute.

  • 29 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9291
  • No canonical URL

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

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 164 internal links, 16 external

    The homepage links to 164 pages on a1fenceproducts.com and 16 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “A-1 Fence is the best fencing company in India, offering perimeter security fence and perimeter fencing solutions. Trus…”.

  • One H1 headline

    Your main headline reads: “Protecting Assets, Borders & People”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Fence Company, Manufacturers, Perimeter fencing solutions”.

  • Structured data in place

    Structured data found: LocalBusiness and Organization.

  • 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.a-1fenceproducts.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.a-1fenceproducts.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

3 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,169 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 63 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “eapps.Platform throws: "Widget "49a512df-c4ed-4966-ae9f-0fd0517677b9" can`t be initialized because WIDGET_NOT_FOUND" wi…”.

2 checks passed
  • Tap targets are thumb-sized

    13 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix95
  • A 15-field form

    Your longest form asks for 15 fields (6 required). Every extra field lowers completion.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 2,234 words of copy

    The homepage carries about 2,234 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us” and “CONTACT US”.

  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks and 18 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Hotjar and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Microsoft Clarity (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 26 other companies contacted

    Loading the homepage contacts 26 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 a1fenceproducts.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 Analytics | Google Tag Manager | Hotjar
Hosting
PrivateSystems Networks

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on a1fenceproducts.com, including 21 speed issues, 3 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

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