Website review, no card needed
adm.ee website review
Visit site (opens in a new tab)Reviewed 19 October 202614 issues · 85 checks
This review found 14 issues worth fixing on adm.ee, 3 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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
93AClosest competitors among reviewed websites
Compare side by sideOne 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
adm.ee does not allow embedding, so this is Google's rendering of the page.
Speed
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.
Use efficient cache lifetimes
700 ms · 72 KiB3 files are served with short cache lifetimes, so returning visitors download them again (72 KiB).
2 third-party services on the page
2 third-party services load with your homepage (Cookiebot and Google Tag Manager), adding 212 KiB and 217 ms of main-thread time.
Reduce unused JavaScript
121 KiBAbout 121 KiB of JavaScript is downloaded but never used on this page.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 79 ms. During a long task the page ignores taps.
Reduce unused CSS
78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page.
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.
3 checks passed
Mobile performance score: 93
93/100Your mobile performance score is 93 (desktop: 99). That is in Google's “good” band (90 and up).
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 259 ms of it running JavaScript. That is comfortably low.
Server response: 26 ms
26 msYour server sent the HTML in 26 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ADM specializes in developing custom software solutions tha…”. Most of its time is element render delay (1.3 s).
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Time to Interactive: 4.0 s
4.0 sThe page becomes fully interactive after 4.0 s. Good is under 3.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 39 ms
39 msScripts block the page for only 39 ms while loading. Good is under 200 ms.
Images and page weight
About 0.1 g of CO₂ per visit
0.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.13 g of CO₂e: 16.0 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: 481 KiB in 30 requests
481 KiBYour homepage downloads 481 KiB in 30 requests on a phone: scripts 293 KiB (14), stylesheets 94 KiB (6) and fonts 49 KiB (3). 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
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (320 characters)
Your meta description is 320 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
214 internal links, 11 external
The homepage links to 214 pages on adm.ee and 11 external pages.
7 checks passed
One H1 headline
Your main headline reads: “ADM specializes in developing custom software solutions that seamlessly integrate digital marketing and cloud with the …”.
Title: 54 characters
Your title is a healthy 54 characters: “ADM – the biggest digital solutions agency in Estonia.”.
Canonical URL set
The canonical URL is https://www.adm.ee/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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.adm.ee/sitemap_index.xml.
AI search readiness
No llms.txt
There is no /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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,437 words), so crawlers that don't run JavaScript still read it.
Other pages
13 pages without a meta description
/solutions, /solutions-categories/strategy-and-consultation, /the-adm-product-thinking-program, /solutions/digital-marketing-strategy, /solutions/service-design and /solutions-categories/design and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example /solutions, whose canonical is /et/lahendused. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page slow to respond
/solutions/atlassians-product-consultation took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 93 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.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
14 of 15 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
1 broken link to your own pages
1 link from your homepage to your own site is broken, for example https://www.adm.ee/solutions/ios-and-android-app-development/ (404).
No HSTS header
No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
6 checks passed
Served over HTTPS
The homepage is served over HTTPS (adm.ee).
Valid certificate (170 days left)
The certificate from SSL Corporation · SSL.com TLS Issuing RSA CA R1 verifies for adm.ee and is valid for another 170 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
http:// redirects to https
http://adm.ee redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
Domain and trust
No CAA record
adm.ee has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
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 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 834 words of copy
The homepage carries about 834 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Contact Us”.
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Contact Us” and “Subscribe”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 22 testimonial or review blocks and “Over 370 clients”.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 2 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Email authentication
Email authentication score: 95/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication, and sends you reports.
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 ip4:167.89.76.131 ip4:80.235.103.32/27 ip4:52.16.192.54 a:directo.gate.ee include:spf.protection.outlook.com inc…”.
DKIM signing found
A DKIM key is published (selector “selector2” and “k2”), so receivers can verify mail really came from you.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
Upkeep, stack and company
- The footer still says © 2024.
- It runs WordPress 6.6.10; the current release is 7.1.3.
Stack
- CMS
- WordPress 6.6.10
- Framework
- jQuery
- Analytics
- Google Tag Manager | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This free review found 14 issues on adm.ee, including 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.