Website review, no card needed
mtg.in website review
Visit site (opens in a new tab)Reviewed 4 November 202652 issues · 88 checks
This review found 52 issues worth fixing on mtg.in, 24 of them high impact, across 88 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
64D- #108,403 of 115,138 reviewed websitesbeats 5%
- #64,580 of 66,397 online storesbeats 2%
- #2,442 of 2,627 WooCommerce storesbeats 6%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.2 s |
| Oct 24, 2026 | 4.3 s |
| Oct 31, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 186 ms |
| May 23, 2026 | 187 ms |
| May 30, 2026 | 191 ms |
| Jun 6, 2026 | 194 ms |
| Jun 13, 2026 | 195 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 192 ms |
| Jul 4, 2026 | 192 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 195 ms |
| Jul 25, 2026 | 197 ms |
| Aug 1, 2026 | 198 ms |
| Aug 8, 2026 | 202 ms |
| Aug 15, 2026 | 205 ms |
| Aug 22, 2026 | 209 ms |
| Aug 29, 2026 | 211 ms |
| Sep 5, 2026 | 211 ms |
| Sep 12, 2026 | 212 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 215 ms |
| Oct 3, 2026 | 218 ms |
| Oct 10, 2026 | 220 ms |
| Oct 17, 2026 | 222 ms |
| Oct 24, 2026 | 225 ms |
| Oct 31, 2026 | 228 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
Speed
Render-blocking requests
2.4 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,660 HTML elements
The page has 7,660 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
800 ms · 13.8 MB50 images could be 13.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
Reduce unused JavaScript
610 ms · 545 KiBAbout 545 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 543 KiB33 files are served with short cache lifetimes, so returning visitors download them again (543 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 854 KiB and 784 ms of main-thread time.
Reduce unused CSS
460 ms · 66 KiBAbout 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 409 ms. During a long task the page ignores taps.
Google Tag Manager adds 306 ms
306 msGoogle Tag Manager costs a phone 306 ms of main-thread work and 367 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.
Facebook adds 305 ms
305 msFacebook costs a phone 305 ms of main-thread work and 313 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
150 ms · 13 KiB13 KiB could be saved by minifying CSS.
Minify JavaScript
37 KiB37 KiB could be saved by minifying JavaScript.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.6 s
2.6 sReal visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 40.9 s
40.9 sYour largest element takes 40.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 48.0 s
48.0 sThe page becomes fully interactive after 48.0 s. Good is under 3.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Real-user INP: 227 ms
227 msReal visitors wait 227 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 186 ms to 228 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 46% slower for real visitors
+46%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
43 images without width and height
43 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
2 checks passed
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 17.7 MB in 185 requests
17.7 MBYour homepage downloads 17.7 MB in 185 requests on a phone: images 15.9 MB (78), scripts 1.5 MB (58) and fonts 150 KiB (3). Under 2 MB keeps phones on slow connections fast.
12 images over 500 KB
12 images weigh 12.4 MB together. On a phone connection a single image that size takes seconds.
18 images far larger than shown
10.2 MB18 images are downloaded at several times the size a phone draws them, for example vocab-ninja-web-banner.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 10.2 MB.
12 images in older formats
12 images (12.4 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.
About 5.0 g of CO₂ per visit
5.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.02 g of CO₂e: 602.5 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
Unlabelled dropdowns
5 dropdowns have no label.
46 text elements with low contrast
46 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
33 tap targets too small
33 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
127 images without alt text
127 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
48 links without text
48 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (37 elements)
ARIA role should be appropriate for the element: 37 elements on the page fail this check, rated minor by axe-core.
21 form fields without a label
21 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (90 characters)
Your title is 90 characters, so Google will cut it off around 60: “Publisher of Best Books for NEET, JEE, Olympiads and School Textbooks - MTG Learning Media”.
24 links crawlers can't follow
24 links have no real href, so search engines can't follow them.
Meta description is long (171 characters)
Your meta description is 171 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.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1,662 internal links, 37 external
The homepage links to 1,662 pages on mtg.in and 37 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://mtg.in/.
Structured data in place
Structured data found: BreadcrumbList, 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://mtg.in/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://mtg.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (6,901 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
2 broken images
2 images failed to load on a phone, for example https://mtgpublicwp.mtg.in/wp-content/themes/neve-child/img/arrow1.png.
23 small tap targets
23 of 113 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
38 distorted images
38 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “PushEngage: Cannot read properties of undefined (reading 'addEventListener')”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 8-field form
Your longest form asks for 8 fields (1 required). Every extra field lowers completion.
About 1,128 words of copy
The homepage carries about 1,128 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “New to MTG? Register”.
41 calls to action
The homepage has 41 calls to action, for example “Class 1 Catalogue – Download Now”, “Class 2 Catalogue – Download Now” and “Class 3 Catalogue – Download Now”.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
23 other companies contacted
Loading the homepage contacts 23 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 mtg.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
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 2 open roles
- Job board
- careers page
- Careers page
- mtg.in/career-with-mtg (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on mtg.in, including 25 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.