Website review, no card needed

mponline.gov.in logo

mponline.gov.in website review

Visit site (opens in a new tab)Reviewed 31 October 202660 issues · 93 checks

This review found 60 issues worth fixing on mponline.gov.in, 28 of them high impact, across 93 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

Real-visitor load time (LCP)75th percentile, phones
4.2 s1.7 sAug 1Oct 243.9 s
Show as table
DateReal-visitor load time (LCP)
Aug 1, 20262.0 s
Aug 8, 20263.3 s
Aug 15, 20263.5 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.7 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20264.0 s
Oct 17, 20263.9 s
Oct 24, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
314 ms272 msAug 1Oct 24281 ms
Show as table
DateReal-visitor tap response (INP)
Aug 1, 2026309 ms
Aug 8, 2026282 ms
Aug 15, 2026279 ms
Aug 22, 2026278 ms
Aug 29, 2026278 ms
Sep 5, 2026284 ms
Sep 12, 2026287 ms
Sep 19, 2026292 ms
Sep 26, 2026284 ms
Oct 3, 2026279 ms
Oct 10, 2026277 ms
Oct 17, 2026277 ms
Oct 24, 2026281 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 mponline.gov.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mponline.gov.in at 2.4 s2.4 s
  2. mponline.gov.in at 4.9 s4.9 s
  3. mponline.gov.in at 7.3 s7.3 s
  4. mponline.gov.in at 9.8 s9.8 s
  5. mponline.gov.in at 12.2 s12.2 s
  6. mponline.gov.in at 14.6 s14.6 s
  7. mponline.gov.in at 17.1 s17.1 s
  8. mponline.gov.in at 19.5 s19.5 s

Speed

10 to fix9
  • Render-blocking requests

    7.9 s

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

  • Use efficient cache lifetimes

    4.3 s · 1.2 MB

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

  • Reduce unused JavaScript

    2.9 s · 496 KiB

    About 496 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.

  • Reduce unused CSS

    1.9 s · 474 KiB

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

  • Main-thread work: 10.1 s

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

  • Mobile performance score: 9

    9/100

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

  • 8 long tasks on the main thread

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

  • Improve image delivery

    750 ms · 656 KiB

    33 images could be 656 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • Google Tag Manager adds 385 ms

    385 ms

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

  • Minify CSS

    310 ms · 92 KiB

    92 KiB could be saved by minifying CSS.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, ux4g.gov.in and Google/Doubleclick Ads and others), adding 344 KiB and 406 ms of main-thread time.

  • Minify JavaScript

    160 ms · 60 KiB

    60 KiB could be saved by minifying JavaScript.

  • Document request latency

    56 KiB

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

  • 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: 287 ms

    287 ms

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

Core Web Vitals

14 to fix0
  • 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: 4.1 s

    4.1 s

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

  • Real-user CLS: 1.13

    1.13

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • First Contentful Paint: 8.9 s

    8.9 s

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

  • Largest Contentful Paint: 15.6 s

    15.6 s

    Your largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Carousel Image”.

  • Speed Index: 16.7 s

    16.7 s

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

  • Time to Interactive: 21.3 s

    21.3 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • Cumulative Layout Shift: 0.422

    0.422

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

  • Real-user INP: 275 ms

    275 ms

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

  • Largest content (LCP) got 51% slower for real visitors

    +51%

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

Images and page weight

3 to fix65
  • Page weight: 3.8 MB in 148 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 148 requests on a phone: images 1.6 MB (81), scripts 1.1 MB (29) and stylesheets 647 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

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

  • 2 images far larger than shown

    101 KiB

    2 images are downloaded at several times the size a phone draws them, for example Internship3.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 101 KiB.

  • 7 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.06 g

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

Accessibility

14 to fixGoogle 6678
  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Positive tabindex

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

  • 13 text elements with low contrast

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

  • 11 tap targets too small

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

  • 50 images without alt text

    50 images have no alt text, which hurts accessibility and image search.

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

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

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

  • 8 links without text

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

  • 5 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

7 to fixGoogle 9268
  • No H1 headline

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

  • 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 (201 characters)

    Your meta description is 201 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://mponline.gov.in/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at mponline.gov.in/robots.txt, the first file search crawlers ask for.

  • Only 4 internal links

    The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

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

2 checks passed
  • Title: 63 characters

    Your title is a healthy 63 characters: “MPOnline Portal | Official Citizen Services Portal - Govt of MP”.

  • Canonical URL set

    The canonical URL is https://www.mponline.gov.in/portal.

AI search readiness

1 to fix81
  • 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://mponline.gov.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.

1 checks passed
  • Text is in the HTML

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

Other pages

3 to fix83
  • 4 linked pages hidden from search

    https://mponline.gov.in/portal/default.aspx, https://mponline.gov.in/portal/services/pancard/home.aspx, https://mponline.gov.in/Portal/CitizenHome.aspx and https://mponline.gov.in/Portal/AboutMPOnline.aspx are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://mponline.gov.in/portal/default.aspx, https://mponline.gov.in/portal/services/pancard/home.aspx and https://mponline.gov.in/Portal/CitizenHome.aspx have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://mponline.gov.in/portal/default.aspx, https://mponline.gov.in/portal/services/pancard/home.aspx, https://mponline.gov.in/Portal/CitizenHome.aspx and https://mponline.gov.in/Portal/AboutMPOnline.aspx have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://mponline.gov.in/portal/default.aspx, https://mponline.gov.in/portal/services/pancard/home.aspx, https://mponline.gov.in/Portal/CitizenHome.aspx and https://mponline.gov.in/Portal/AboutMPOnline.aspx took over 3 s to send their HTML from our server.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 4 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 4 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6574
  • 1 broken image

    1 image failed to load on a phone, for example https://mponline.gov.in/portal/IndexNewUtil/images/MPONLINEkiosk.png.

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Missing catch or finally after try”.

  • 6 distorted images

    6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 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 532 words of copy

    The homepage carries about 532 words of visible text.

3 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 mponline.gov.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
jQuery
Analytics
Google Analytics
Hosting
MPOnline Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 60 issues on mponline.gov.in, including 24 speed issues, 7 SEO issues and 3 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