aaft.com website review

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

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

The page has 3,174 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 908 ms of main-thread work and 715 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 CDN costs a phone 849 ms of main-thread work and 1.1 MB 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.

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

Facebook costs a phone 268 ms of main-thread work and 226 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.

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

4 images could be 114 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Polyfills for old browsers add 13 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

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

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Your homepage downloads 4.3 MB in 149 requests on a phone: scripts 2.2 MB (30), other files 714 KiB (23) and images 573 KiB (67). Under 2 MB keeps phones on slow connections fast.

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

7 dropdowns have no label.

Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

Some list items are not inside a list.

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

1 link inside paragraphs relies on colour alone to stand out.

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

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

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

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

Your title is 84 characters, so Google will cut it off around 60: “Cinema, Journalism, Fashion, Animation, Interior & Music College in Delhi NCR | AAFT”.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 459 pages on aaft.com and 9 external pages.

/school-of-advertising and /school-of-music took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187060480&tm=gtm002&Ver=2&mid=721cd8cd-e166-4889-babd-1ad32cbf9023&bo=1&sid=8e789000d8ae11f1899cbb3cf3491d59&vid=8e78a920d8ae11f19a24d56773298086&vids=1&msclkid=N&pi=9.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

A form field blocks pasting, which frustrates password managers and people on phones.

1 image is served at too low a resolution for sharp phone screens.

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.

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.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 8 fields (6 required). Every extra field lowers completion.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

DMARC is set to p=none, so mail pretending to be aaft.com is still delivered. Reports are on, so moving to quarantine is the next step.

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, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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 12 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.