Website review, no card needed

statiq.in logo

statiq.in website review

Visit site (opens in a new tab)Reviewed 31 October 202626 issues · 78 checks

This review found 26 issues worth fixing on statiq.in, 8 of them high impact, across 78 checks. The most urgent: page weight: 11.5 MB in 147 requests. 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
3.7 s2.0 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20262.8 s
Sep 5, 20263.2 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.3 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Oct 24, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
205 ms168 msMay 9Oct 24197 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026175 ms
May 16, 2026174 ms
May 23, 2026173 ms
May 30, 2026172 ms
Jun 6, 2026172 ms
Jun 13, 2026173 ms
Jun 20, 2026172 ms
Jun 27, 2026172 ms
Jul 4, 2026173 ms
Jul 11, 2026173 ms
Jul 18, 2026173 ms
Jul 25, 2026173 ms
Aug 1, 2026173 ms
Aug 8, 2026173 ms
Aug 15, 2026177 ms
Aug 22, 2026179 ms
Aug 29, 2026182 ms
Sep 5, 2026182 ms
Sep 12, 2026182 ms
Sep 19, 2026183 ms
Sep 26, 2026188 ms
Oct 3, 2026194 ms
Oct 10, 2026200 ms
Oct 17, 2026201 ms
Oct 24, 2026197 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 statiq.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. statiq.in at 1.1 s1.1 s
  2. statiq.in at 2.2 s2.2 s
  3. statiq.in at 3.3 s3.3 s
  4. statiq.in at 4.4 s4.4 s
  5. statiq.in at 5.5 s5.5 s
  6. statiq.in at 6.6 s6.6 s
  7. statiq.in at 7.7 s7.7 s
  8. statiq.in at 8.8 s8.8 s

Speed

8 to fix75
  • Main-thread work: 4.3 s

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

  • Use efficient cache lifetimes

    9.7 MB

    31 files are served with short cache lifetimes, so returning visitors download them again (9.7 MB).

  • Improve image delivery

    1.2 MB

    13 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 75

    75/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.5 MB and 648 ms of main-thread time.

  • Reduce unused JavaScript

    556 KiB

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

  • Google Tag Manager adds 257 ms

    257 ms

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

  • zohocdn.com adds 47 ms

    47 ms

    zohocdn.com costs a phone 47 ms of main-thread work and 530 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.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    58 KiB

    Polyfills for old browsers add 58 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    13 KiB

    About 13 KiB of CSS is downloaded but never applied on this page.

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

1 checks passed
  • Server response: 496 ms

    496 ms

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

Core Web Vitals

5 to fix100
  • 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.

  • Time to Interactive: 19.1 s

    19.1 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Total Blocking Time: 630 ms

    630 ms

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

  • Real-user TTFB: 911 ms

    911 ms

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

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

7 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 191 ms

    191 ms

    Real visitors wait 191 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.

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.003

    0.003

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.9 s

    0.9 s

    Your largest element renders in 0.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Building the largest network of EV chargers in India”.

Images and page weight

2 to fix60
  • Page weight: 11.5 MB in 147 requests

    11.5 MB

    Your homepage downloads 11.5 MB in 147 requests on a phone: media 7.9 MB (4), scripts 1.8 MB (57) and images 1.5 MB (23). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    29 KiB

    1 image is downloaded at several times the size a phone draws it, for example Bmw.png at 400 px wide, shown at 85 px. Resized copies would save about 29 KiB.

  • 4 images in older formats

    4 images (171 KiB) 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.

  • About 3.3 g of CO₂ per visit

    3.27 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.27 g of CO₂e: 391.8 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

4 to fixGoogle 9193
  • 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.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 7 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • 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 X (Twitter) card tag

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

  • 32 internal links, 22 external

    The homepage links to 32 pages on statiq.in and 22 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Statiq is building EV charging stations in India with a fast-growing network, smart software, and scalable solutions fo…”.

  • One H1 headline

    Your main headline reads: “Building the largest network of EV chargers in India”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “EV Charging Stations in India | Fast Charging Network - Statiq”.

  • Canonical URL set

    The canonical URL is https://www.statiq.in/.

  • Structured data in place

    Structured data found: FAQPage, MobileApplication, Organization, WebPage and WebSite.

  • 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.statiq.in/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 1 page without an H1

    https://www.statiq.in/privacy-policy-page has 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 19 found) and read each the way a search engine does.

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

  • 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 to fixGoogle 9285
  • 5 small tap targets

    5 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 1,877 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: “SHOP” and “Download App”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop”, “Download App” and “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 90 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 21 other companies contacted

    Loading the homepage contacts 21 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 statiq.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on statiq.in, including 13 speed issues, 1 SEO issue 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