Website review, no card needed
10thmagnitude.com website review
Visit site (opens in a new tab)Reviewed 19 October 202620 issues · 78 checks
This review found 20 issues worth fixing on 10thmagnitude.com, 4 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.9 s |
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 208 ms |
| May 2, 2026 | 202 ms |
| May 9, 2026 | 193 ms |
| May 16, 2026 | 189 ms |
| May 23, 2026 | 182 ms |
| May 30, 2026 | 182 ms |
| Jun 6, 2026 | 181 ms |
| Jun 13, 2026 | 180 ms |
| Jun 20, 2026 | 182 ms |
| Jun 27, 2026 | 182 ms |
| Jul 4, 2026 | 185 ms |
| Jul 11, 2026 | 185 ms |
| Jul 18, 2026 | 188 ms |
| Jul 25, 2026 | 189 ms |
| Aug 1, 2026 | 186 ms |
| Aug 8, 2026 | 189 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 186 ms |
| Aug 29, 2026 | 186 ms |
| Sep 5, 2026 | 185 ms |
| Sep 12, 2026 | 184 ms |
| Sep 19, 2026 | 181 ms |
| Sep 26, 2026 | 184 ms |
| Oct 3, 2026 | 185 ms |
| Oct 10, 2026 | 185 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
Speed
3,456 HTML elements
The page has 3,456 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
450 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Reduce unused CSS
150 ms · 68 KiBAbout 68 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
164 KiBAbout 164 KiB of JavaScript is downloaded but never used on this page.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
14 KiB1 file is served with short cache lifetimes, so returning visitors download them again (14 KiB).
Improve image delivery
11 KiB1 image could be 11 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
10 KiB10 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
3 KiB3 KiB could be saved by minifying CSS.
2 third-party services on the page
2 third-party services load with your homepage (Other Google APIs/SDKs and Pardot), adding 15 KiB and 0 ms of main-thread time.
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100 (desktop: 67). That is in Google's “good” band (90 and up).
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 497 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 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: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 4.8 s
4.8 sThe page becomes fully interactive after 4.8 s. Good is under 3.8 s.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Real-user INP: 186 ms
186 msReal visitors wait 186 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 208 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Speed Index: 2.2 s
2.2 sVisually, the page fills in at 2.2 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Largest Contentful Paint: 1.4 s
1.4 sYour largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “People listening to someone in a meeting”.
Total Blocking Time: 49 ms
49 msScripts block the page for only 49 ms while loading. Good is under 200 ms.
Images and page weight
About 0.2 g of CO₂ per visit
0.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.16 g of CO₂e: 19.3 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: 581 KiB in 90 requests
581 KiBYour homepage downloads 581 KiB in 90 requests on a phone: scripts 178 KiB (38), fonts 159 KiB (4) and images 116 KiB (8). 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 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h2 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
34 links with vague text
34 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
39 internal links, 6 external
The homepage links to 39 pages on 10thmagnitude.com and 6 external pages.
7 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “As a leading innovator on the Microsoft platform, Cognizant brings our consultancy, industry experience and expertise t…”.
One H1 headline
Your main headline reads: “Engineering modern business in the era of AI”.
Title: 41 characters
Your title is a healthy 41 characters: “Microsoft Platform Innovation | Cognizant”.
Canonical URL set
The canonical URL is https://www.cognizant.com/us/en/services/cloud-solutions/microsoft-business-group.
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.cognizant.com/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,819 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.cognizant.com/llms.txt (86 KiB, 392 links), a plain-text guide to the site for AI tools.
Other pages
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.cognizant.com/us/en/services/infrastructure-services/digital-workplace-services, whose canonical is https://www.cognizant.com/us/en/services/cloud-solutions/digital-workplace-services. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://www.cognizant.com/us/en/case-studies/healthcare-technical-debt, https://www.cognizant.com/us/en/case-studies/optimizing-banking-cloud-costs, https://www.cognizant.com/us/en/case-studies/corelogic-rapid-power-automate-migration, https://www.cognizant.com/us/en/case-studies/oup-reduces-risk-and-gets-future-ready-with-modern-it-estate, https://www.cognizant.com/us/en/case-studies/community-fibre-automation and https://www.cognizant.com/us/en/case-studies/vorwerk-prepares-for-growth-with-new-digital-sales-platform and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
3 small tap targets
3 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
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 404 ()”.
1 checks passed
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.
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.
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.
About 790 words of copy
The homepage carries about 790 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “contact-us-iframe”.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 2 trust badges.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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).
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 10thmagnitude.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 20 issues on 10thmagnitude.com, including 7 speed issues, 2 SEO issues and 3 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.