Website review, no card needed
alkemy.com website review
Visit site (opens in a new tab)Reviewed 19 October 202648 issues · 87 checks
This review found 48 issues worth fixing on alkemy.com, 19 of them high impact, across 87 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.2 s |
| May 2, 2026 | 4.3 s |
| May 9, 2026 | 4.2 s |
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 183 ms |
| May 2, 2026 | 195 ms |
| May 9, 2026 | 180 ms |
| May 16, 2026 | 183 ms |
| May 23, 2026 | 197 ms |
| May 30, 2026 | 200 ms |
| Jun 6, 2026 | 207 ms |
| Jun 13, 2026 | 206 ms |
| Jun 20, 2026 | 189 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 156 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 155 ms |
| Aug 1, 2026 | 155 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 206 ms |
| Aug 29, 2026 | 206 ms |
| Sep 5, 2026 | 223 ms |
| Sep 12, 2026 | 175 ms |
| Sep 19, 2026 | 189 ms |
| Sep 26, 2026 | 189 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 182 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
Render-blocking requests
1.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Main-thread work: 5.9 s
A phone's processor spends 5.9 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,376 HTML elements
The page has 3,376 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
7.8 MB67 files are served with short cache lifetimes, so returning visitors download them again (7.8 MB).
Improve image delivery
2.4 MB59 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Cookiebot and others), adding 2.0 MB and 960 ms of main-thread time.
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 49). Pages that score under 90 lose visitors before the first paint.
Google CDN adds 396 ms
396 msGoogle CDN costs a phone 396 ms of main-thread work and 1.1 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 334 ms
334 msGoogle Tag Manager costs a phone 334 ms of main-thread work and 594 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 365 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
Reduce unused CSS
10 KiBAbout 10 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.
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: 6 ms
6 msYour server sent the HTML in 6 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.
Time to Interactive: 26.3 s
26.3 sThe page becomes fully interactive after 26.3 s. Good is under 3.8 s.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 841 ms
841 msScripts block taps and scrolling for 841 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
76 images without width and height
76 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 183 ms to 182 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.2 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 172 ms
172 msReal visitors wait 172 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 2.1 s
2.1 sYour largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 11.6 MB in 135 requests
11.6 MBYour homepage downloads 11.6 MB in 135 requests on a phone: media 5.4 MB (1), scripts 2.6 MB (29) and images 2.6 MB (70). Under 2 MB keeps phones on slow connections fast.
17 images far larger than shown
1.3 MB17 images are downloaded at several times the size a phone draws them, for example AlkemyPluslogo.png at 4,096 px wide, shown at 120 px. Resized copies would save about 1.3 MB.
28 images in older formats
28 images (1.8 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.
About 3.3 g of CO₂ per visit
3.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.29 g of CO₂e: 395.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
Orphan list items
Some list items are not inside a list.
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is short (67 characters)
Your meta description is only 67 characters: “We design business evolution through data, technology & creativity.”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected property name or '}' in JSON at position 4 (line 2 )”.
No XML sitemap
No XML sitemap at https://www.alkemy.com/sitemap.xml, so Google discovers your pages only by following links.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
7 internal links, 3 external
The homepage links to 7 pages on alkemy.com and 3 external pages.
4 checks passed
Title: 49 characters
Your title is a healthy 49 characters: “Alkemy Group | Designed by humans. Powered by AI.”.
Canonical URL set
The canonical URL is https://www.alkemy.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.
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://www.alkemy.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,848 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.alkemy.com/investors, which answers with an error. Visitors hit a dead end and search engines drop it.
3 pages point its canonical at the homepage
https://www.alkemy.com/en/insights, https://www.alkemy.com/es and https://www.alkemy.com/latam declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
5 pages share a title
https://www.alkemy.com/en, https://www.alkemy.com/en/insights, /, https://www.alkemy.com/es and https://www.alkemy.com/latam all use the title “Alkemy Group | Designed by humans. Powered by AI.”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without an H1
/ and https://www.alkemy.com/es have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.alkemy.com/en/insights, / and https://www.alkemy.com/latam took over 3 s to send their HTML from our server.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Every page has a meta description
All 4 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
16 small tap targets
16 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
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 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.
Thin social proof
Social proof on the homepage: “More than 1000 clients”. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 2,846 words of copy
The homepage carries about 2,846 words of visible text.
2 checks passed
Direct contact links
Visitors can reach you directly: 0 phone links and 9 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
14 other companies contacted
Loading the homepage contacts 14 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.
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 alkemy.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- Next.js
Company
- Founded
- 2012
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on alkemy.com, including 20 speed issues, 5 SEO issues and 4 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.