edukemy.com website review

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

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

10 images could be 728 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

Your mobile performance score is 58 (desktop: 72). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Google/Doubleclick Ads and others), adding 1.1 MB and 736 ms of main-thread time.

About 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

76 KiB could be saved by minifying JavaScript.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying CSS.

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.

Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Geo 1 on 1”.

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

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

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

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

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

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

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

Your homepage downloads 5.0 MB in 98 requests on a phone: images 3.4 MB (28), scripts 1.3 MB (23) and stylesheets 143 KiB (23). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example explore_printed_books.webp at 1,512 px wide, shown at 366 px. Resized copies would save about 91 KiB.

4 images (172 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.

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

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

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

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

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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 on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 48 pages on edukemy.com and 7 external pages.

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.

There is no /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.

/upsc declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /upsc all use the title “Edukemy: Best Online & Offline Coaching for UPSC Exams in India”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/upsc-current-affairs, /refer-and-earn and /free-resources-for-upsc have no meta description, so Google writes the search snippet from whatever text it finds.

/upsc has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “pidTracker is not defined”.

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

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://forms.office.com/r/XLgjLMZMaV.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

edukemy.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

edukemy.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 333 words of visible text.

edukemy.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 6 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.