Website review, no card needed
silvertouch.com website review
Visit site (opens in a new tab)Reviewed 1 November 202651 issues · 98 checks
This review found 51 issues worth fixing on silvertouch.com, 22 of them high impact, across 98 checks. The most urgent: reduce unused JavaScript. 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 7.8 s |
| May 16, 2026 | 8.4 s |
| May 23, 2026 | 8.5 s |
| May 30, 2026 | 8.6 s |
| Jun 6, 2026 | 8.5 s |
| Jun 13, 2026 | 8.1 s |
| Jun 20, 2026 | 7.9 s |
| Jun 27, 2026 | 7.8 s |
| Jul 4, 2026 | 7.8 s |
| Jul 11, 2026 | 7.9 s |
| Jul 18, 2026 | 7.6 s |
| Jul 25, 2026 | 7.3 s |
| Aug 1, 2026 | 6.8 s |
| Aug 8, 2026 | 5.8 s |
| Aug 15, 2026 | 5.6 s |
| Aug 22, 2026 | 5.6 s |
| Aug 29, 2026 | 5.6 s |
| Sep 5, 2026 | 5.6 s |
| Sep 12, 2026 | 6.0 s |
| Sep 19, 2026 | 6.2 s |
| Sep 26, 2026 | 6.3 s |
| Oct 3, 2026 | 6.4 s |
| Oct 10, 2026 | 6.3 s |
| Oct 17, 2026 | 6.1 s |
| Oct 24, 2026 | 6.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 243 ms |
| May 16, 2026 | 236 ms |
| May 23, 2026 | 227 ms |
| May 30, 2026 | 230 ms |
| Jun 6, 2026 | 232 ms |
| Jun 13, 2026 | 240 ms |
| Jun 20, 2026 | 242 ms |
| Jun 27, 2026 | 253 ms |
| Jul 4, 2026 | 253 ms |
| Jul 11, 2026 | 247 ms |
| Jul 18, 2026 | 240 ms |
| Jul 25, 2026 | 240 ms |
| Aug 1, 2026 | 227 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 228 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 220 ms |
| Sep 5, 2026 | 220 ms |
| Sep 12, 2026 | 213 ms |
| Sep 19, 2026 | 216 ms |
| Sep 26, 2026 | 212 ms |
| Oct 3, 2026 | 216 ms |
| Oct 10, 2026 | 222 ms |
| Oct 17, 2026 | 223 ms |
| Oct 24, 2026 | 232 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.5 s
1.0 s
1.4 s
1.9 s
2.4 s
2.9 s
3.3 s
3.8 s
Speed
Reduce unused JavaScript
4.0 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
2.3 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Use efficient cache lifetimes
1.1 s · 230 KiB9 files are served with short cache lifetimes, so returning visitors download them again (230 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Hotjar and others), adding 1.5 MB and 943 ms of main-thread time.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
450 ms · 481 KiB29 images could be 481 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 368 ms
368 msGoogle Tag Manager costs a phone 368 ms of main-thread work and 837 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.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
300 ms · 62 KiBAbout 62 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google CDN adds 173 ms
173 msGoogle CDN costs a phone 173 ms of main-thread work and 349 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.
2,057 HTML elements
The page has 2,057 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 153 ms. During a long task the page ignores taps.
Minify JavaScript
35 KiB35 KiB could be saved by minifying JavaScript.
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 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.
1 checks passed
Server response: 109 ms
109 msYour server sent the HTML in 109 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: 6.6 s
6.6 sReal visitors wait 6.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.8 s
5.8 sReal visitors see the first content after 5.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.3 s
2.3 sReal visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 18.5 s
18.5 sYour largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DIGITAL TRANSFORMATION Drive efficiency & agility with our …”.
Time to Interactive: 30.2 s
30.2 sThe page becomes fully interactive after 30.2 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
Real-user INP: 218 ms
218 msReal visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
65 images without width and height
65 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 263 ms
263 msScripts block taps and scrolling for 263 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 243 ms to 232 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 7.8 s to 6.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 6.2 MB in 172 requests
6.2 MBYour homepage downloads 6.2 MB in 172 requests on a phone: scripts 3.7 MB (32), images 1.2 MB (95) and other files 703 KiB (15). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
198 KiB3 images are downloaded at several times the size a phone draws them, for example Home-E-Governance-Services.png at 600 px wide, shown at 80 px. Resized copies would save about 198 KiB.
6 images in older formats
6 images (338 KiB) 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.
4 images below the first screen load straight away
4 images further down the page (149 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.76 g of CO₂e: 211.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
9 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (9 elements)
Certain ARIA roles must contain particular children: 9 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (9 elements)
ARIA attributes must conform to valid values: 9 elements on the page fail this check, rated critical by axe-core.
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
2 dropdowns have no label.
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (14 elements)
Interactive controls must not be nested: 14 elements on the page fail this check, rated serious by axe-core.
ARIA input fields must have an accessible name (9 elements)
ARIA input fields must have an accessible name: 9 elements on the page fail this check, rated serious by axe-core.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA toggle fields must have an accessible name (3 elements)
ARIA toggle fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.
70 images without alt text
70 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements marked as presentational should be consistently ignored (9 elements)
Elements marked as presentational should be consistently ignored: 9 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 66 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 13 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (78 characters)
Your title is 78 characters, so Google will cut it off around 60: “IT Solutions, Managed Security Services, Digital Transformation | Silver Touch”.
4 H1 headlines
There are 4 <h1> headlines (“DIGITAL”, “SECURITY SERVICES” and “PEOPLE & GOVERNMENT”). One clear main headline is easier for people and search engines.
Meta description is long (165 characters)
Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
114 internal links, 43 external
The homepage links to 114 pages on silvertouch.com and 43 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.silvertouch.com/.
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://www.silvertouch.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.silvertouch.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.
3 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,152 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
40 small tap targets
40 of 123 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 807 words of copy
The homepage carries about 807 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
9 calls to action
The homepage has 9 calls to action, for example “Call Center / IP Telephony”, “Contact” and “Learn More”.
Social proof on the page
Social proof on the homepage: 4 customer or partner logos, 3 trust badges and “2000+ Clients”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and Hotjar.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel 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.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (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.
21 other companies contacted
Loading the homepage contacts 21 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 silvertouch.com, 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 | Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Coreix Ltd
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on silvertouch.com, including 22 speed issues, 5 SEO issues and 4 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.