Website review, no card needed
aethir.com website review
Visit site (opens in a new tab)Reviewed 21 October 202649 issues · 88 checks
This review found 49 issues worth fixing on aethir.com, 20 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.1 s |
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 236 ms |
| May 9, 2026 | 215 ms |
| May 16, 2026 | 206 ms |
| May 23, 2026 | 213 ms |
| May 30, 2026 | 244 ms |
| Jun 6, 2026 | 222 ms |
| Jun 13, 2026 | 214 ms |
| Jun 20, 2026 | 211 ms |
| Jun 27, 2026 | 199 ms |
| Jul 4, 2026 | 213 ms |
| Jul 11, 2026 | 242 ms |
| Jul 18, 2026 | 215 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 200 ms |
| Aug 15, 2026 | 221 ms |
| Aug 22, 2026 | 217 ms |
| Aug 29, 2026 | 210 ms |
| Sep 5, 2026 | 217 ms |
| Sep 12, 2026 | 215 ms |
| Sep 19, 2026 | 226 ms |
| Sep 26, 2026 | 229 ms |
| Oct 3, 2026 | 211 ms |
| Oct 10, 2026 | 196 ms |
| Oct 17, 2026 | 194 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
Use efficient cache lifetimes
16.7 s · 10.6 MB56 files are served with short cache lifetimes, so returning visitors download them again (10.6 MB).
Improve image delivery
13.8 s · 8.6 MB4 images could be 8.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.8 s faster on a phone.
Reduce unused JavaScript
2.5 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 26
26/100Your mobile performance score is 26 (desktop: 35). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.9 s
A phone's processor spends 9.9 s on main-thread work while loading, 7.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 5.5 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and LinkedIn Ads and others), adding 2.2 MB and 1.8 s of main-thread time.
YouTube adds 578 ms
578 msYouTube costs a phone 578 ms of main-thread work and 970 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.
Reduce unused CSS
300 ms · 111 KiBAbout 111 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.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 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: 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: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 23.1 s
23.1 sYour largest element takes 23.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Predictive Oncology Launches Aethir (ATH) Digital Asset Tre…”.
Speed Index: 21.0 s
21.0 sVisually, the page fills in at 21.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 51.8 s
51.8 sThe page becomes fully interactive after 51.8 s. Good is under 3.8 s.
Total Blocking Time: 3.7 s
3.7 sScripts block taps and scrolling for 3.7 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Real-user INP: 230 ms
230 msReal visitors wait 230 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
29 images without width and height
29 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 236 ms to 194 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 12.9 MB in 127 requests
12.9 MBYour homepage downloads 12.9 MB in 127 requests on a phone: images 9.1 MB (30), scripts 3.5 MB (45) and fonts 115 KiB (4). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
aethir_cube.png weighs 2.6 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
1.9 MB1 image is downloaded at several times the size a phone draws it, for example aethir_cube.png at 2,007 px wide, shown at 358 px. Resized copies would save about 1.9 MB.
1 image in older formats
1 image (2.6 MB) is 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 3.7 g of CO₂ per visit
3.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.66 g of CO₂e: 439.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (7 elements)
Headings should not be empty: 7 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 30 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (13 characters)
Your title is only 13 characters: “Home | Aethir”. 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.
Meta description is short (40 characters)
Your meta description is only 40 characters: “Powerful GPU compute solutions on-demand”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“Home” and “Powerful GPU compute solutions on-demand”). One clear main headline is easier for people and search engines.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
24 internal links, 42 external
The homepage links to 24 pages on aethir.com and 42 external pages.
4 checks passed
Canonical URL set
The canonical URL is http://aethir.com/.
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://aethir.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.
No llms.txt
There is no https://aethir.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 (440 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://aethir.com/ai all use the title “Home | Aethir”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://aethir.com/blog-posts/cutting-costs-not-corners-edge-computing-for-game-studios and https://aethir.com/blog-posts/cloud-gaming-face-off-centralized-vs-decentralized-systems have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://aethir.com/gaming, https://aethir.com/ecosystem-fund, https://aethir.com/aethir-forge and https://aethir.com/ai-unbundled use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://aethir.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 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.
3 JavaScript errors while loading
3 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”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
7 of 7 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 371 words of copy
The homepage carries about 371 words of visible text.
2 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Contact Us”, “Learn More” and “Get Started”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and The Trade Desk and 2 mores (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
26 other companies contacted
Loading the homepage contacts 26 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 aethir.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 49 issues on aethir.com, including 21 speed issues, 6 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.