codetantra.com website review

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

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

28 images could be 712 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.

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

About 145 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 760 ms faster on a phone.

65 KiB could be saved by minifying JavaScript.

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

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

8 files are served with short cache lifetimes, so returning visitors download them again (162 KiB).

7 KiB could be saved by minifying CSS.

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

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

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

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 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Exchanging Memorandum of Understanding between Chairman AIC…”.

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

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

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

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

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

4 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' tap response (inp) went from 109 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.2 MB in 170 requests on a phone: images 4.7 MB (158), scripts 300 KiB (4) and HTML 102 KiB (1). Under 2 MB keeps phones on slow connections fast.

39 images (2.2 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.

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

1 image is downloaded at several times the size a phone draws it, for example Feb16-2021-MoU-between-AICTE-and-CodeTantra.jpg at 1,600 px wide, shown at 294 px. Resized copies would save about 121 KiB.

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

There are 2 <h1> headlines (“Your virtual university, in minutes!” and “Your virtual univ/school, in minutes!”). One clear main headline is easier for people and search engines.

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

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 at https://www.codetantra.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at codetantra.com/robots.txt, the first file search crawlers ask for.

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

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

The homepage links to 161 pages on codetantra.com and 4 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.

/, /123.jsp, /contact-us.jsp, /privacy-policy.jsp and /about-us.jsp all use the title “Teach & Learn Anywhere - CodeTantra”. Search engines can't tell which page to show for a search, so each competes with the others.

/buy.jsp, /python-programing-course-details.jsp, /java-course-details.jsp, /c-programing-course-details.jsp, /cpp-programing-course-details.jsp and /hadoop-course-details.jsp and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/123.jsp, /contact-us.jsp, /privacy-policy.jsp and /about-us.jsp use the same meta description. A description written for each page earns more clicks.

/123.jsp, /buy.jsp, /python-programing-course-details.jsp, /java-course-details.jsp, /c-programing-course-details.jsp and /cpp-programing-course-details.jsp and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

/123.jsp has 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.

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

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

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

4 links go through two or more redirects, for example http://codetantra.com/?d=iitk.

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.

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

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

Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 715 words of visible text.

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

Opening the homepage sets 7 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.