Website review, no card needed
eisd.net website review
Visit site (opens in a new tab)Reviewed 29 October 202654 issues · 77 checks
This review found 54 issues worth fixing on eisd.net, 25 of them high impact, across 77 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
51FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 172 ms |
| May 16, 2026 | 167 ms |
| May 23, 2026 | 165 ms |
| May 30, 2026 | 167 ms |
| Jun 6, 2026 | 165 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 157 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 142 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 141 ms |
| Jul 25, 2026 | 151 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 178 ms |
| Aug 15, 2026 | 180 ms |
| Aug 22, 2026 | 186 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 185 ms |
| Sep 12, 2026 | 192 ms |
| Sep 19, 2026 | 198 ms |
| Sep 26, 2026 | 205 ms |
| Oct 3, 2026 | 217 ms |
| Oct 10, 2026 | 220 ms |
| Oct 17, 2026 | 222 ms |
| Oct 24, 2026 | 222 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
9.5 s · 4.2 MB36 files are served with short cache lifetimes, so returning visitors download them again (4.2 MB).
Reduce unused JavaScript
7.8 s · 3.7 MBAbout 3.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.8 s faster on a phone.
Improve image delivery
2.9 s · 3.9 MB16 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.
YouTube adds 2.3 s
2.3 sYouTube costs a phone 2.3 s of main-thread work and 4.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.
Render-blocking requests
1.6 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 11
11/100Your mobile performance score is 11. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.0 s
A phone's processor spends 9.0 s on main-thread work while loading, 5.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Google CDN and others), adding 11.7 MB and 3.3 s of main-thread time.
Reduce unused CSS
450 ms · 366 KiBAbout 366 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
apptegy.net adds 63 ms
63 msapptegy.net costs a phone 63 ms of main-thread work and 5.8 MB 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.
Google Tag Manager adds 380 ms
380 msGoogle Tag Manager costs a phone 380 ms of main-thread work and 533 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.
Google CDN adds 345 ms
345 msGoogle CDN costs a phone 345 ms of main-thread work and 741 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 374 ms. During a long task the page ignores taps.
alwayson.ai adds 78 ms
78 msalwayson.ai costs a phone 78 ms of main-thread work and 382 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.
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: 21 ms
21 msYour server sent the HTML in 21 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 CLS: 0.31
0.31For real visitors the layout shifts by 0.31 (75th percentile). Good is under 0.1.
First Contentful Paint: 14.3 s
14.3 sThe first text or image appears after 14.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 32.1 s
32.1 sYour largest element takes 32.1 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 27.2 s
27.2 sVisually, the page fills in at 27.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 66.8 s
66.8 sThe page becomes fully interactive after 66.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.637
0.637The layout shifts by 0.637 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 929 ms
929 msScripts block taps and scrolling for 929 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 252 ms
252 msReal visitors wait 252 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 172 ms to 222 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user TTFB: 702 ms
702 msReal visitors wait 702 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 14.7 MB in 243 requests
14.7 MBYour homepage downloads 14.7 MB in 243 requests on a phone: scripts 6.3 MB (39), images 6.0 MB (37) and other files 1.2 MB (137). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
9cee8012-591c-483e-8d35-95d21241bdef.jpeg weighs 567 KiB. On a phone connection a single image that size takes seconds.
4 images far larger than shown
778 KiB4 images are downloaded at several times the size a phone draws them, for example 9cee8012-591c-483e-8d35-95d21241bdef.jpeg at 1,399 px wide, shown at 310 px. Resized copies would save about 778 KiB.
5 images in older formats
5 images (1.4 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.
1 image below the first screen load straight away
1 image further down the page (261 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.2 g of CO₂ per visit
4.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.16 g of CO₂e: 499.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Links must have discernible text (4 elements)
Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (16 characters)
Your title is only 16 characters: “Client Challenge”. 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 canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 XML sitemap
No XML sitemap at https://www.eisd.net/sitemap.xml, so Google discovers your pages only by following links.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1 checks passed
robots.txt in place
robots.txt is in place.
AI search readiness
Most text only appears after JavaScript runs
5%A phone browser shows 755 words, but the HTML your server sends has only 35. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.eisd.net/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.
1 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.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
59 of 60 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 755 words of copy
The homepage carries about 755 words of visible text.
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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
20 other companies contacted
Loading the homepage contacts 20 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 eisd.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on eisd.net, including 27 speed issues, 10 SEO issues and 5 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.