codevidhya.com website review

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.1 MB and 1.0 s of main-thread time.

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

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

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

Google CDN costs a phone 311 ms of main-thread work and 734 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.

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

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

tidio.co costs a phone 82 ms of main-thread work and 515 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.

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

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

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

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

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 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Coding Curriculum for Kids We mentor young learners to thri…”.

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

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

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

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

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

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

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

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

Your homepage downloads 4.6 MB in 69 requests on a phone: scripts 2.3 MB (25), images 1.5 MB (12) and other files 361 KiB (18). Under 2 MB keeps phones on slow connections fast.

3 images (109 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.

1 image further down the page (32 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

Some list items are not inside a list.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 28 characters: “Coding For Kids - Codevidhya”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 7 <h1> headlines (“Coding Curriculum for Kids”, “800+” and “44+”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 66 pages on codevidhya.com and 5 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/terms-of-use is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/terms-of-use, /yearone-course, /yeartwo-courses, /yearten-course, /certification-courses and /python-pcap and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/terms-of-use, /yearone-course, /yeartwo-courses, /yearten-course, /certification-courses and /python-pcap and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

/terms-of-use, /yearone-course, /yeartwo-courses, /yearten-course, /certification-courses and /python-pcap and 2 others took over 3 s to send their HTML from our server.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'querySelector')”.

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

Chrome logged issues while loading the page (“Cookie”).

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.

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.

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

DMARC is set to p=none, so mail pretending to be codevidhya.com is still delivered. Add a report address, check the reports, then move to quarantine.

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, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 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.

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