Website review, no card needed
amala.earth website review
Visit site (opens in a new tab)Reviewed 20 October 202657 issues · 79 checks
This review found 57 issues worth fixing on amala.earth, 21 of them high impact, across 79 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
48F- #123,931 of 124,051 reviewed websitesbeats 0%
- #69,756 of 69,761 online storesbeats 0%
- #63,447 of 63,450 Shopify storesbeats 0%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.7 s |
| May 9, 2026 | 4.8 s |
| May 16, 2026 | 4.7 s |
| May 23, 2026 | 4.9 s |
| May 30, 2026 | 5.1 s |
| Jun 6, 2026 | 5.3 s |
| Jun 13, 2026 | 5.1 s |
| Jun 20, 2026 | 4.9 s |
| Jun 27, 2026 | 4.8 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.5 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 158 ms |
| May 9, 2026 | 157 ms |
| May 16, 2026 | 161 ms |
| May 23, 2026 | 180 ms |
| May 30, 2026 | 197 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 206 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 190 ms |
| Jul 11, 2026 | 186 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 156 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 167 ms |
| Aug 22, 2026 | 176 ms |
| Aug 29, 2026 | 182 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 181 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 175 ms |
| Oct 3, 2026 | 169 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 165 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
12.6 s · 9.3 MB26 files are served with short cache lifetimes, so returning visitors download them again (9.3 MB).
Improve image delivery
11.3 s · 8.8 MB19 images could be 8.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.3 s faster on a phone.
Reduce unused JavaScript
4.8 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Render-blocking requests
1.8 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 32
32/100Your mobile performance score is 32 (desktop: 25). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Facebook and others), adding 12.4 MB and 1.0 s of main-thread time.
cloudfront.net adds 608 ms
608 mscloudfront.net costs a phone 608 ms of main-thread work and 11.7 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.
Reduce unused CSS
300 ms · 49 KiBAbout 49 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 319 ms. During a long task the page ignores taps.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 209 ms
209 msGoogle Tag Manager costs a phone 209 ms of main-thread work and 352 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.
Facebook adds 189 ms
189 msFacebook costs a phone 189 ms of main-thread work and 314 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
150 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.63
0.63For real visitors the layout shifts by 0.63 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 55.0 s
55.0 sYour largest element takes 55.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 56.8 s
56.8 sThe page becomes fully interactive after 56.8 s. Good is under 3.8 s.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.591
0.591The layout shifts by 0.591 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 353 ms
353 msReal visitors wait 353 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Total Blocking Time: 383 ms
383 msScripts block taps and scrolling for 383 ms in total while the page loads. Good is under 200 ms.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
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.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 158 ms to 165 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.7 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user TTFB: 726 ms
726 msReal visitors wait 726 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 13.2 MB in 141 requests
13.2 MBYour homepage downloads 13.2 MB in 141 requests on a phone: images 11.1 MB (42), scripts 1.5 MB (43) and other files 594 KiB (48). Under 2 MB keeps phones on slow connections fast.
About 3.8 g of CO₂ per visit
3.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.75 g of CO₂e: 450.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Headings should not be empty (5 elements)
Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
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.
Blocked from indexing
Google's crawler is blocked from indexing this page.
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.
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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
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://amala.earth/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://amala.earth/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 small tap targets
5 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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_BLOCKED_BY_RESPONSE.NotSameOrigin”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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.
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.
Only about 55 words
The homepage has only about 55 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
Analytics in place
Analytics detected: Meta Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
16 other companies contacted
Loading the homepage contacts 16 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 amala.earth, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- E-commerce
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on amala.earth, including 24 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.