Website review, no card needed

gppetroleums.co.in logo

gppetroleums.co.in website review

Visit site (opens in a new tab)Reviewed 4 November 202643 issues · 85 checks

This review found 43 issues worth fixing on gppetroleums.co.in, 23 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
4.4 s3.7 sMay 16Oct 314.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.4 s
May 23, 20264.2 s
May 30, 20264.1 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20263.9 s
Jun 27, 20264.0 s
Jul 4, 20263.9 s
Jul 11, 20263.8 s
Jul 18, 20263.8 s
Jul 25, 20263.8 s
Aug 1, 20264.1 s
Aug 8, 20264.1 s
Aug 15, 20264.2 s
Aug 22, 20264.3 s
Aug 29, 20264.2 s
Sep 5, 20264.2 s
Sep 12, 20264.2 s
Sep 19, 20264.1 s
Sep 26, 20264.1 s
Oct 3, 20264.0 s
Oct 10, 20264.1 s
Oct 17, 20263.9 s
Oct 24, 20264.2 s
Oct 31, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
108 ms89 msMay 16Oct 31106 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202698 ms
May 23, 202698 ms
May 30, 2026101 ms
Jun 6, 202698 ms
Jun 13, 202698 ms
Jun 20, 202696 ms
Jun 27, 202695 ms
Jul 4, 202696 ms
Jul 11, 202697 ms
Jul 18, 202697 ms
Jul 25, 202696 ms
Aug 1, 202693 ms
Aug 8, 202691 ms
Aug 15, 202692 ms
Aug 22, 202693 ms
Aug 29, 202695 ms
Sep 5, 202695 ms
Sep 12, 202696 ms
Sep 19, 2026100 ms
Sep 26, 2026103 ms
Oct 3, 2026103 ms
Oct 10, 2026105 ms
Oct 17, 202694 ms
Oct 24, 202696 ms
Oct 31, 2026106 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 gppetroleums.co.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gppetroleums.co.in at 1.2 s1.2 s
  2. gppetroleums.co.in at 2.5 s2.5 s
  3. gppetroleums.co.in at 3.7 s3.7 s
  4. gppetroleums.co.in at 4.9 s4.9 s
  5. gppetroleums.co.in at 6.2 s6.2 s
  6. gppetroleums.co.in at 7.4 s7.4 s
  7. gppetroleums.co.in at 8.6 s8.6 s
  8. gppetroleums.co.in at 9.9 s9.9 s

Speed

10 to fix7
  • Improve image delivery

    8.2 s · 2.1 MB

    8 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.2 s faster on a phone.

  • Render-blocking requests

    4.4 s

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

  • Reduce unused CSS

    1.8 s · 272 KiB

    About 272 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Font display

    1.5 s

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

  • Google CDN adds 1.3 s

    1.3 s

    Google CDN costs a phone 1.3 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 10.4 s

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

  • Mobile performance score: 7

    7/100

    Your mobile performance score is 7. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts and others), adding 1.3 MB and 1.5 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.

  • Reduce unused JavaScript

    554 KiB

    About 554 KiB of JavaScript is downloaded but never used on this page.

  • Minify CSS

    150 ms · 21 KiB

    21 KiB could be saved by minifying CSS.

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.3 s

    5.3 s

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 26.3 s

    26.3 s

    Your largest element takes 26.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 16.3 s

    16.3 s

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

  • Time to Interactive: 26.4 s

    26.4 s

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

  • Cumulative Layout Shift: 0.964

    0.964

    The layout shifts by 0.964 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • 18 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 98 ms to 106 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-10-31, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user INP: 114 ms

    114 ms

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

  • Real-user CLS: 0.00

    0.00

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

Images and page weight

4 to fix33
  • Page weight: 6.5 MB in 128 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 128 requests on a phone: images 2.7 MB (27), fonts 1.7 MB (12) and scripts 1.3 MB (47). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    655 KiB

    2 images are downloaded at several times the size a phone draws them, for example PLANT-PHOTO-1-scaled.jpeg at 2,560 px wide, shown at 326 px. Resized copies would save about 655 KiB.

  • 5 images in older formats

    5 images (1.1 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 below the first screen load straight away

    1 image further down the page (430 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.83 g

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

Accessibility

6 to fixGoogle 8893
  • 19 text elements with low contrast

    19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (10 elements)

    All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

  • 6 form fields without a label

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

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (1 element)

    Headings should not be empty: 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 (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

6 to fixGoogle 7775
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • 9 H1 headlines

    There are 9 <h1> headlines (“India's Largest Manufacturer”, “and Supplier of Cutting Coolant” and “IPOL”). One clear main headline is easier for people and search engines.

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

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 57 internal links, 6 external

    The homepage links to 57 pages on gppetroleums.co.in and 6 external pages.

4 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “GP Petroleums (GPPL) – Passion for Growth !”.

  • Canonical URL set

    The canonical URL is https://gppetroleums.co.in/.

  • 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://gppetroleums.co.in/wp-sitemap.xml.

AI search readiness

1 to fix88
  • 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://gppetroleums.co.in/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.

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://gppetroleums.co.in/our-story, https://gppetroleums.co.in/milestones, https://gppetroleums.co.in/board-of-directors, https://gppetroleums.co.in/leadership, https://gppetroleums.co.in/our-business and https://gppetroleums.co.in/disclosure-under-reg-46-of-the-lodr-2/memorandum-and-articles-of-association and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://gppetroleums.co.in/our-story, https://gppetroleums.co.in/milestones, https://gppetroleums.co.in/board-of-directors, https://gppetroleums.co.in/leadership, https://gppetroleums.co.in/our-business and https://gppetroleums.co.in/disclosure-under-reg-46-of-the-lodr-2/memorandum-and-articles-of-association 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 39 found) and read each the way a search engine does.

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

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

Best practices

1 to fixGoogle 9684
  • 10 broken images

    10 images failed to load on a phone, for example https://themeholy.com/wordpress/malen/wp-content/uploads/2023/05/about_shape2.png.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: “900+ Happy Customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 406 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

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

  • 3 calls to action

    The homepage has 3 calls to action, for example “Investor Contact” and “Contact Us”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 2 email links.

Privacy and tracking

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 gppetroleums.co.in, 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
Hosting
GoDaddy

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on gppetroleums.co.in, including 21 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