Website review, no card needed

silverskills.com logo

silverskills.com website review

Visit site (opens in a new tab)Reviewed 19 November 202646 issues · 95 checks

This review found 46 issues worth fixing on silverskills.com, 15 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.6 s3.0 sMay 30Nov 143.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.0 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20263.9 s
Jun 27, 20263.8 s
Jul 4, 20263.7 s
Jul 11, 20263.4 s
Jul 18, 20263.3 s
Jul 25, 20263.4 s
Aug 1, 20263.5 s
Aug 8, 20263.7 s
Aug 15, 20264.2 s
Aug 22, 20264.4 s
Aug 29, 20264.2 s
Sep 5, 20264.0 s
Sep 12, 20263.8 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Oct 17, 20263.7 s
Oct 24, 20263.6 s
Oct 31, 20263.7 s
Nov 7, 20263.4 s
Nov 14, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
166 ms103 msMay 30Nov 14110 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026146 ms
Jun 6, 2026138 ms
Jun 13, 2026143 ms
Jun 20, 2026138 ms
Jun 27, 2026142 ms
Jul 4, 2026143 ms
Jul 11, 2026148 ms
Jul 18, 2026152 ms
Jul 25, 2026152 ms
Aug 1, 2026155 ms
Aug 8, 2026156 ms
Aug 15, 2026159 ms
Aug 22, 2026153 ms
Aug 29, 2026146 ms
Sep 5, 2026138 ms
Sep 12, 2026129 ms
Sep 19, 2026126 ms
Sep 26, 2026124 ms
Oct 3, 2026122 ms
Oct 10, 2026119 ms
Oct 17, 2026125 ms
Oct 24, 2026125 ms
Oct 31, 2026125 ms
Nov 7, 2026115 ms
Nov 14, 2026110 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

Full-page screenshot of silverskills.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. silverskills.com at 1.2 s1.2 s
  2. silverskills.com at 2.4 s2.4 s
  3. silverskills.com at 3.5 s3.5 s
  4. silverskills.com at 4.7 s4.7 s
  5. silverskills.com at 5.9 s5.9 s
  6. silverskills.com at 7.1 s7.1 s
  7. silverskills.com at 8.3 s8.3 s
  8. silverskills.com at 9.4 s9.4 s

Speed

15 to fix55
  • Use efficient cache lifetimes

    4.2 s · 5.4 MB

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

  • Reduce unused JavaScript

    3.6 s · 606 KiB

    About 606 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

  • Render-blocking requests

    3.5 s

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

  • Improve image delivery

    1.6 s · 1.8 MB

    18 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

  • Mobile performance score: 55

    55/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and cdn-cookieyes.com and others), adding 1.7 MB and 751 ms of main-thread time.

  • Document request latency

    700 ms · 153 KiB

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

  • Reduce initial server response time

    696 ms

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

  • Reduce unused CSS

    500 ms · 107 KiB

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

  • Legacy JavaScript

    450 ms · 67 KiB

    Polyfills for old browsers add 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

  • Google CDN adds 347 ms

    347 ms

    Google CDN costs a phone 347 ms of main-thread work and 739 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.0 s

    A phone's processor spends 3.0 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Tag Manager adds 213 ms

    213 ms

    Google Tag Manager costs a phone 213 ms of main-thread work and 640 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,225 HTML elements

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

  • Server response: 796 ms

    796 ms

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

  • 11 long tasks on the main thread

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

  • Minify JavaScript

    9 KiB

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 32.5 s

    32.5 s

    Your largest element takes 32.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, serve p…”.

  • Speed Index: 22.0 s

    22.0 s

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

  • Time to Interactive: 34.0 s

    34.0 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • 19 images without width and height

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

6 checks passed
  • Real-user INP: 110 ms

    110 ms

    Real visitors wait 110 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 21% faster for real visitors

    -21%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 146 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 18% faster for real visitors

    -18%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 144 ms

    144 ms

    Scripts block the page for only 144 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix43
  • Page weight: 7.6 MB in 142 requests

    7.6 MB

    Your homepage downloads 7.6 MB in 142 requests on a phone: images 5.0 MB (77), scripts 1.8 MB (32) and other files 377 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 40 images in older formats

    40 images (3.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.

  • 9 images below the first screen load straight away

    9 images further down the page (788 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    98 KiB

    2 images are downloaded at several times the size a phone draws them, for example society.png at 886 px wide, shown at 234 px. Resized copies would save about 98 KiB.

  • About 2.1 g of CO₂ per visit

    2.14 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 257.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

11 to fixGoogle 7386
  • 7 buttons without a name

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • All page content should be contained by landmarks (58 elements)

    All page content should be contained by landmarks: 58 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 5 links without text

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

  • 2 form fields without a label

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 105 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9295
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • 232 internal links, 17 external

    The homepage links to 232 pages on silverskills.com and 17 external pages.

7 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Silverskills offers industry-leading business process management and digital transformation services. Partner with us t…”.

  • One H1 headline

    Your main headline reads: “Integrating Business Process Management and Digital Transformation for Sustainable Growth”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Silverskills | Business Process Management & Transformation”.

  • Canonical URL set

    The canonical URL is https://www.silverskills.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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.silverskills.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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://www.silverskills.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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,345 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.silverskills.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.silverskills.com/digital-transformation/services/labs, https://www.silverskills.com/products/intellispread, https://www.silverskills.com/products/mustang, https://www.silverskills.com/products/doculytical, https://www.silverskills.com/products/sheets-think and https://www.silverskills.com/products/volition took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 73 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 8591
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to script at 'https://cdn-in.pagesense.io/js/silverskills/17531348baa6443cbaccb0653dfa9b4d.js' from origin 'http…”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    35 of 36 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 1,107 words of copy

    The homepage carries about 1,107 words of visible text.

5 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us” and “Quote to Cash”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 7 customer or partner logos and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 2 email links.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and LinkedIn Insight (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 2 of them by other companies (measured from a US location before any click).

  • 15 other companies contacted

    Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 silverskills.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on silverskills.com, including 24 speed issues, 2 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25