ttkprestige.com website review

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

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

About 823 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.5 s faster on a phone.

Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

45 images could be 8.3 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.

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

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

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

91 KiB could be saved by minifying CSS.

6 third-party services load with your homepage (Google Tag Manager, Google CDN and FontAwesome CDN and others), adding 1.0 MB and 380 ms of main-thread time.

Google Tag Manager costs a phone 209 ms of main-thread work and 299 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.1 s on main-thread work while loading, 544 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

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

12 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

The layout shifts by 0.545 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 15.2 MB in 164 requests on a phone: images 12.2 MB (120), scripts 1.4 MB (21) and stylesheets 932 KiB (14). Under 2 MB keeps phones on slow connections fast.

8 images weigh 6.7 MB together. On a phone connection a single image that size takes seconds.

16 images are downloaded at several times the size a phone draws them, for example MicrosoftTeams-image-4.png at 1,873 px wide, shown at 340 px. Resized copies would save about 4.7 MB.

38 images (10.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.

28 images further down the page (7.9 MB) 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 4.31 g of CO₂e: 516.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), 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 24 characters: “Home Page - TTK Prestige”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“The Prestige Touch” and “Follow Us On Social @ttkprestige”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 22 pages on ttkprestige.com and 120 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 https://www.ttkprestige.com/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.

Your homepage links to https://www.ttkprestige.com/Qe4VUc8n8rFI-ZX3uQUgorKEAMK-TorD-ngCN_jMins=.html, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.ttkprestige.com/corporate, https://www.ttkprestige.com/corporate/our-stores, https://www.ttkprestige.com/corporate/about-us, https://www.ttkprestige.com/corporate/investor-centre, https://www.ttkprestige.com/corporate/people-careers and https://www.ttkprestige.com/corporate/our-business and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ttkprestige.com/corporate, https://www.ttkprestige.com/corporate/our-stores, https://www.ttkprestige.com/corporate/investor-centre, https://www.ttkprestige.com/corporate/our-stores/enquiry-form, https://www.ttkprestige.com/corporate/people-careers and https://www.ttkprestige.com/corporate/our-business and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.ttkprestige.com/.

5 of 24 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 “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v6.4.0/css/all.css?wpfas=true&ver=1.0.0' from origin …”.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Ads, 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 2 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.