Website review, no card needed

stpi.in logo

stpi.in website review

Visit site (opens in a new tab)Reviewed 1 November 202656 issues · 89 checks

This review found 56 issues worth fixing on stpi.in, 25 of them high impact, across 89 checks. The most urgent: render-blocking 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

Full-page screenshot of stpi.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

15 to fix49
  • Render-blocking requests

    22.4 s

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

  • Reduce unused CSS

    5.1 s · 1.0 MB

    About 1.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.1 s faster on a phone.

  • Improve image delivery

    3.1 s · 1.8 MB

    28 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 3.1 s faster on a phone.

  • Use efficient cache lifetimes

    2.1 s · 1.9 MB

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

  • Reduce unused JavaScript

    1.6 s · 985 KiB

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

  • Font display

    1.4 s

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

  • Mobile performance score: 49

    49/100

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

  • Main-thread work: 4.2 s

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

  • Minify CSS

    750 ms · 156 KiB

    156 KiB could be saved by minifying CSS.

  • Minify JavaScript

    600 ms · 207 KiB

    207 KiB could be saved by minifying JavaScript.

  • Document request latency

    650 ms · 145 KiB

    The HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    643 ms

    Reduce initial server response time. Google estimates savings of 643 ms on a phone.

  • Google Tag Manager adds 438 ms

    438 ms

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

  • 2,668 HTML elements

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

  • Server response: 743 ms

    743 ms

    Your server takes 743 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google CDN and others), adding 359 KiB and 487 ms of main-thread time.

  • 11 long tasks on the main thread

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

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

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.

  • First Contentful Paint: 18.2 s

    18.2 s

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

  • Largest Contentful Paint: 24.6 s

    24.6 s

    Your largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “इन्क्यूबेशन”.

  • Speed Index: 20.8 s

    20.8 s

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

  • Time to Interactive: 28.1 s

    28.1 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Total Blocking Time: 290 ms

    290 ms

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

  • 6 images without width and height

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

3 checks passed
  • Real-user INP: 165 ms

    165 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 19.9 MB in 208 requests

    19.9 MB

    Your homepage downloads 19.9 MB in 208 requests on a phone: images 14.8 MB (100), scripts 3.1 MB (36) and stylesheets 1.4 MB (61). Under 2 MB keeps phones on slow connections fast.

  • 18 images over 500 KB

    18 images weigh 8.9 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    1.5 MB

    8 images are downloaded at several times the size a phone draws them, for example Ministry_of_Electronics_and_Information_Technology.svg at 2,180 px wide, shown at 243 px. Resized copies would save about 1.5 MB.

  • 36 images in older formats

    36 images (12.9 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.

  • 7 images below the first screen load straight away

    7 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.6 g of CO₂ per visit

    5.64 g

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

Accessibility

6 to fixGoogle 8992
  • 21 tap targets too small

    21 tap targets are too small or too close together to hit reliably with a finger.

  • Positive tabindex

    13 elements have a tabindex above 0, which scrambles the keyboard order.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (7 elements).

2 checks passed
  • Every image has alt text

    All 90 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 6139
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • 45 links crawlers can't follow

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

  • Title is long (118 characters)

    Your title is 118 characters, so Google will cut it off around 60: “सॉफ्टवेयर टेक्नोलॉजी पार्क्स ऑफ इंडिया | इलेक्ट्रॉनिकी और सूचना प्रौद्योगिकी मंत्रालय,इले…”.

  • No structured data

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

  • Meta description is long (175 characters)

    Your meta description is 175 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 XML sitemap

    No XML sitemap at https://xn--m1bet8dtc8dtcb.xn--h2brj9c/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 203 internal links, 126 external

    The homepage links to 203 pages on stpi.in and 126 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://xn--m1bet8dtc8dtcb.xn--h2brj9c/en.

  • robots.txt in place

    robots.txt is in place.

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://xn--m1bet8dtc8dtcb.xn--h2brj9c/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

3 to fix83
  • 6 linked pages hidden from search

    https://xn--m1bet8dtc8dtcb.xn--h2brj9c/en, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/main-know-your-minister, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/stpi-annual-reports, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/main-newsletters, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/main-tenders and https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/circulars-notifications are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/main-know-your-minister, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/stpi-annual-reports, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/main-newsletters, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/main-tenders and https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/circulars-notifications have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://xn--m1bet8dtc8dtcb.xn--h2brj9c/en has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/screen-reader, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/governing-council, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/stpi-management-structure, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/director-general-stpi, https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/stpi-jurisdictional-directors and https://xn--m1bet8dtc8dtcb.xn--h2brj9c/hi/stpi-iso-certificates and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 22 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

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

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

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 125 words

    The homepage has only about 125 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 6 cookies set on arrival

    6

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 stpi.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
Drupal
Framework
jQuery
Analytics
Google Analytics
Hosting
Software Technology Parks of India - Bangalore

Company

Founded
1991
Headquarters
New Delhi

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 56 issues on stpi.in, including 25 speed issues, 9 SEO issues and 5 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