SEO report for parcoengineers.com

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to parcoengineers.com…

Indexing & crawling 100%

Can search engines reach, read and index this page?

• ✓

  Status codecritical

  The page returned HTTP 200.

• ✓

  Indexablecritical

  No noindex instruction – the page can appear in search.

• ✓

  robots.txthigh

  robots.txt found.

  Googlebot is allowed to crawl this page.

• ✓

  XML sitemaphigh

  Sitemap index found at https://parcoengineers.com/sitemap_index.xml listing 4 sitemaps.

  Declared in robots.txt.

  Most recent lastmod: 2026-11-03T05:36:35+00:00.

• ✓

  Canonical URLhigh

  Canonical: https://parcoengineers.com/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✓

  www / non-wwwmedium

  www.parcoengineers.com redirects to parcoengineers.com.

Search snippet & sharing 67%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “Best Galvanised Steel & Iron Traders in Mumbai - Parco Engineers”

  About 594px of Google's ~580px desktop width – it will probably be cut off.

  Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the SEO title.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• !

  Meta descriptionhigh

  168 characters, ~1039px of ~990px.

  Long – Google will probably truncate it.

  Google sometimes rewrites descriptions to match the search; a good one is still used most often.

  Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

  On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the meta description.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  Twitter/X card: summary_large_image.

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="en-US"

Content quality 77%

Is there enough clear, useful text that matches what the page targets?

• ✓

  Word countmedium

  3,324 words of main content (menus and footer excluded).

  Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

• !

  Readabilitymedium

  Flesch reading ease 43 (fairly difficult), about 16 words per sentence.

  Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  Read the guide: how to write SEO content

• ✓

  Topic focushigh

  8 of 8 title keywords appear in the main content.

• ✓

  H1 headingcritical

  “YOUR TRUSTED PARTNER IN GALVANIZED STEEL SOLUTIONS”

• ✗

  Heading structuremedium

  94 headings for 3324 words – a lot for the amount of text.

  6 skipped level(s), e.g. H2 → H4.

  Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  Read the guide: the on-page SEO checklist

• !

  Text-to-code ratiolow

  5% of the HTML is visible text.

  Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 88%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

• ✓

  AI crawler accesshigh

  Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

• ✓

  Snippet controlshigh

  No snippet restrictions – search and AI answers can quote this page.

• ✓

  llms.txtlow

  /llms.txt found.

• !

  Question-led contentmedium

  2 heading(s) phrased as questions, e.g. “WHY GALVANIZING ?”.

  Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  Read the guide: how to write SEO content

• ✓

  Entity clarityhigh

  Identified as: Organization, LocalBusiness.

  6 official profile link(s) (sameAs).

• ✓

  Freshness signalsmedium

  The page shows when it was published or last updated.

• !

  Trust pages (E-E-A-T)medium

  Links found to about and contact; missing privacy.

  Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 70%

Machine-readable facts for rich results and AI.

• !

  JSON-LD present & validhigh

  6 JSON-LD block(s): WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, Organization, LocalBusiness, PostalAddress.

  Block 2: invalid JSON; Block 5: invalid JSON

  Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).

  Make valid code with the free schema generator

  Read the guide: schema markup

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

  Google now shows FAQ rich results only for well-known government and health sites, but the markup still helps machines read your Q&As.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  118 internal and 9 external links.

• ✗

  Anchor text qualitymedium

  Same text used for different pages: “learn more”, “read more”.

  10 vague link(s) like “click here” or “read more”.

  5 link(s) with no text at all.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

Performance 50%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• !

  Server response (TTFB)high

  1605 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

  Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.

• ✗

  HTML sizemedium

  499 kB of HTML – heavy for phones.

  Fix: Remove inline bloat, base64 images and unused markup.

• ✓

  Compressionmedium

  Compressed with br.

• ✓

  Render-blocking resourceshigh

  0 blocking script(s) and 2 stylesheet(s) in <head>.

• ✗

  Scripts & third partiesmedium

  34 script tag(s); files loaded from 1 other domain(s): fonts.googleapis.com.

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  87 image(s).

  6 without width/height – can cause layout shift (CLS).

  43 image(s) after the first three aren't lazy-loaded.

  36 use WebP/AVIF or responsive srcset.

  Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  On WordPress: Install a free image optimiser plugin (such as EWWW Image Optimizer or Smush) to shrink images and serve WebP.

  Read the guide: image SEO

• !

  Cachinglow

  Cache-Control: no-cache

  Fix: Set Cache-Control so browsers and CDNs can reuse the page.

• ✓

  HTTP/3low

  Server advertises HTTP/3 (faster on mobile networks).

Security 67%

Visitor safety signals that browsers and Google check.

• ✓

  HTTPScritical

  Secure HTTPS with no mixed content.

• ✓

  HTTP → HTTPS redirecthigh

  http:// redirects to https://.

• ✗

  HSTSmedium

  No Strict-Transport-Security header.

  Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  Read the guide: the technical SEO checklist

• ✗

  Security headerslow

  Present: CSP.

  Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  Read the guide: the technical SEO checklist

• ✗

  Server fingerprintlow

  X-Powered-By reveals “PHP/8.3.36”.

  Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 75%

Usable on phones and by everyone – Google indexes the mobile version.

• ✓

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1.0

• ✓

  Image alt textmedium

  All 87 images have alt text.

• ✗

  Form labelsmedium

  6 of 11 form field(s) have no label.

  Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

• ✗

  Link nameslow

  5 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✓

  Tap-to-contactmedium

  One-tap contact: phone and email.

Local SEO 83%

Signals that help you appear in Google Maps and 'near me' searches.

• ✓

  LocalBusiness markuphigh

  LocalBusiness markup includes: address, telephone, geo, openingHoursSpecification, url.

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

  No postcode found (fine for service-area businesses).

  An email link is shown.

• ✗

  Map & directionslow

  No map or directions link.

  Fix: Add a Google Maps directions link so customers can find you.

  Read the guide: the local SEO checklist