Website review, no card needed
savex.in website review
Visit site (opens in a new tab)Reviewed 30 October 202641 issues · 88 checks
This review found 41 issues worth fixing on savex.in, 11 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.5 s |
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.7 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.8 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.6 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 151 ms |
| May 16, 2026 | 148 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 149 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 150 ms |
| Aug 8, 2026 | 150 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 151 ms |
| Sep 5, 2026 | 147 ms |
| Sep 12, 2026 | 148 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 140 ms |
| Oct 3, 2026 | 143 ms |
| Oct 10, 2026 | 143 ms |
| Oct 17, 2026 | 148 ms |
| Oct 24, 2026 | 152 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
Speed
Render-blocking requests
3.6 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
25.4 MB7 files are served with short cache lifetimes, so returning visitors download them again (25.4 MB).
7 third-party services on the page
7 third-party services load with your homepage (YouTube, amcharts.com and Google Tag Manager and others), adding 1.6 MB and 1.0 s of main-thread time.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
915 KiBAbout 915 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
600 ms · 209 KiBAbout 209 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
YouTube adds 467 ms
467 msYouTube costs a phone 467 ms of main-thread work and 1,018 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.
Improve image delivery
350 ms · 120 KiB12 images could be 120 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
amcharts.com adds 414 ms
414 msamcharts.com costs a phone 414 ms of main-thread work and 318 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.
1,957 HTML elements
The page has 1,957 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 193 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 2 KiB2 KiB could be saved by minifying CSS.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 234 ms
234 msYour server sent the HTML in 234 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: 5.2 s
5.2 sReal visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.0 s
5.0 sReal visitors see the first content after 5.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.3 s
3.3 sReal visitors wait 3.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
Real-user INP: 227 ms
227 msReal visitors wait 227 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
41 images without width and height
41 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your trusted ICT distribution partner with over 38 years of…”. Most of its time is element render delay (4.7 s).
Total Blocking Time: 401 ms
401 msScripts block taps and scrolling for 401 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.102
0.102The layout shifts by 0.102 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 151 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.5 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 28.9 MB in 129 requests
28.9 MBYour homepage downloads 28.9 MB in 129 requests on a phone: media 25.3 MB (5), scripts 1.7 MB (37) and images 1.3 MB (27). Under 2 MB keeps phones on slow connections fast.
13 images in older formats
13 images (1.1 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.
About 8.2 g of CO₂ per visit
8.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.19 g of CO₂e: 982.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Skip links are not focusable.
Skip links are not focusable. (1 element).
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 81 images in the HTML carry an alt attribute.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (18 characters)
Your title is only 18 characters: “Savex Technologies”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at savex.in/robots.txt, the first file search crawlers ask for.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
45 internal links, 29 external
The homepage links to 45 pages on savex.in and 29 external pages.
3 checks passed
One H1 headline
Your main headline reads: “Savex Technologies”.
Canonical URL set
The canonical URL is https://savex.in/.
XML sitemap found
Your XML sitemap is reachable at https://savex.in/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://savex.in/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (643 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://savex.in/about-us, https://savex.in/our-alliance, https://savex.in/services, https://savex.in/solutions, https://savex.in/career and https://savex.in/branch-locator and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://savex.in/about-us, https://savex.in/our-alliance, https://savex.in/services, https://savex.in/solutions, https://savex.in/career and https://savex.in/branch-locator and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://savex.in/about-us, https://savex.in/services, https://savex.in/solutions, https://savex.in/compliances, https://savex.in/partner-with-us and https://savex.in/become-a-partner and 1 other took over 3 s to send their HTML from our server.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 11 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
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.
Local business without LocalBusiness data
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 436 words of copy
The homepage carries about 436 words of visible text.
6 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Contact Us”, “Contact : Mr. Jayant Goradia” and “E-order Portal”.
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 2 trust badges and “over 12,000 customers”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 12 phone links and 10 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before 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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).
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.
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at savex.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on savex.in, including 23 speed issues, 6 SEO issues and 2 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.