techilan.com website review

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

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

12 images could be 516 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

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

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

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

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

11 KiB could be saved by minifying JavaScript.

10 KiB could be saved by minifying CSS.

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

2 third-party services load with your homepage (Cloudflare CDN and Google Fonts), adding 22 KiB and 1 ms of main-thread time.

Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Experience Techilan & Ascend a long ladder of success Conta…”. Most of its time is element render delay (6.6 s).

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.0 MB in 49 requests on a phone: images 2.6 MB (25), stylesheets 236 KiB (14) and scripts 144 KiB (6). Under 2 MB keeps phones on slow connections fast.

9 images (1.7 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.

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

2 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 331 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.

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

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

The homepage links to 50 pages on techilan.com and 6 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.

/career and /internship all use the title “Techilan Pvt Ltd | Internship”. Search engines can't tell which page to show for a search, so each competes with the others.

/why-choose-us, /what-we-do, /career, /internship, /blog and /contact-us use the same meta description. A description written for each page earns more clicks.

/why-choose-us, /what-we-do, /salesforce-cloud-services-saleforce-consulting-and-implementation-services, /salesforce-crm-implementation-and-sales-cloud-services, /salesforce-service-cloud-and-salesforce-consulting-with-crm-support and /salesforce-implementation-services-and-consulting-company and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

/contact-us 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.

/what-we-do, /salesforce-cloud-services-saleforce-consulting-and-implementation-services, /salesforce-crm-implementation-and-sales-cloud-services, /free-salesforce-consultation-service, /career and /internship and 3 others took over 3 s to send their HTML from our server.

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

4 images failed to load on a phone, for example https://techilan.com/assets/images/switcher-color/img-1.jpg.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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 1,008 words of visible text.

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