Website review, no card needed
itel-india.com website review
Visit site (opens in a new tab)Reviewed 28 October 202626 issues · 70 checks
This review found 26 issues worth fixing on itel-india.com, 16 of them high impact, across 70 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 11.9 s |
| May 16, 2026 | 14.3 s |
| May 23, 2026 | 14.0 s |
| May 30, 2026 | 15.9 s |
| Jun 6, 2026 | 15.9 s |
| Jun 13, 2026 | 14.8 s |
| Jun 20, 2026 | 15.9 s |
| Jun 27, 2026 | 16.6 s |
| Jul 4, 2026 | 16.2 s |
| Jul 11, 2026 | 16.6 s |
| Jul 18, 2026 | 16.4 s |
| Jul 25, 2026 | 13.6 s |
| Aug 1, 2026 | 13.0 s |
| Aug 8, 2026 | 16.2 s |
| Aug 15, 2026 | 15.6 s |
| Aug 22, 2026 | 16.0 s |
| Aug 29, 2026 | 16.5 s |
| Sep 5, 2026 | 15.0 s |
| Sep 12, 2026 | 14.7 s |
| Sep 19, 2026 | 15.0 s |
| Sep 26, 2026 | 15.1 s |
| Oct 3, 2026 | 16.0 s |
| Oct 10, 2026 | 15.3 s |
| Oct 17, 2026 | 15.0 s |
| Oct 24, 2026 | 14.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 5, 2026 | 612 ms |
| Sep 12, 2026 | 592 ms |
| Sep 19, 2026 | 592 ms |
| Sep 26, 2026 | 542 ms |
| Oct 3, 2026 | 542 ms |
| Oct 10, 2026 | 668 ms |
| Oct 24, 2026 | 721 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
itel-india.com does not allow embedding, so this is Google's rendering of the page.
Speed
Use efficient cache lifetimes
4.2 s · 899 KiB43 files are served with short cache lifetimes, so returning visitors download them again (899 KiB).
Mobile performance score: 78
78/100Your mobile performance score is 78 (desktop: 100). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
900 ms · 82 KiBAbout 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Reduce unused JavaScript
640 ms · 113 KiBAbout 113 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 640 ms faster on a phone.
Improve image delivery
70 KiB6 images could be 70 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 268 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 14.5 s
14.5 sReal visitors wait 14.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 736 ms
736 msReal visitors wait 736 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 12.4 s
12.4 sReal visitors see the first content after 12.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.7 s
5.7 sReal visitors wait 5.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 5.9 s
5.9 sThe page becomes fully interactive after 5.9 s. Good is under 3.8 s.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 612 ms to 721 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 11.9 s to 14.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Speed Index: 2.5 s
2.5 sVisually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.6 s
0.6 sThe first text or image appears after 0.6 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.2 g of CO₂ per visit
0.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.25 g of CO₂e: 30.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 902 KiB in 44 requests
902 KiBYour homepage downloads 902 KiB in 44 requests on a phone: fonts 298 KiB (3), scripts 265 KiB (19) and stylesheets 176 KiB (4). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 2 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
4 checks passed
Structured data in place
Structured data found: Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://itel-india.com/sitemap.xml.
AI search readiness
No llms.txt
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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Best practices
Does not redirect HTTP traffic to HTTPS
Does not redirect HTTP traffic to HTTPS.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
9 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No HTTPS
Your homepage is served without HTTPS, so browsers mark it “Not secure” and some refuse forms on it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
1 checks passed
http:// redirects to https
http://itel-india.com redirects to the secure version.
Domain and trust
No CAA record
itel-india.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.
DNSSEC is off
itel-india.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.
2 checks passed
Domain is 6 years old
6 yearsitel-india.com was registered in Aug 2020 through Amazon Registrar, Inc.. An established domain carries more trust with email providers and search engines.
Registered until Aug 2027
itel-india.com is registered until Aug 2027.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 99 words
The homepage has only about 99 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
Email authentication
No DMARC policy
itel-india.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.
No SPF record
itel-india.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.
No DKIM key on the usual selectors
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.
Domain receives no email
itel-india.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.
Email authentication score: 0/100
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.
Privacy and tracking
No consent tool detected
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on itel-india.com, including 11 speed issues, 5 SEO issues and 6 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.