Website review, no card needed
aerangis.com website review
Visit site (opens in a new tab)Reviewed 17 November 202647 issues · 91 checks
This review found 47 issues worth fixing on aerangis.com, 17 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
4.0 s · 876 KiBAbout 876 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
1.3 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 2.2 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 (Google Tag Manager, Klaviyo and Wishlist King and others), adding 2.6 MB and 1.3 s of main-thread time.
Use efficient cache lifetimes
950 ms · 335 KiB32 files are served with short cache lifetimes, so returning visitors download them again (335 KiB).
Google Tag Manager adds 695 ms
695 msGoogle Tag Manager costs a phone 695 ms of main-thread work and 1,018 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.
2,473 HTML elements
The page has 2,473 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 177 ms
177 msKlaviyo costs a phone 177 ms of main-thread work and 320 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.
Shopify adds 47 ms
47 msShopify costs a phone 47 ms of main-thread work and 838 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.
Improve image delivery
233 KiB10 images could be 233 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
150 ms · 75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.
Legacy JavaScript
100 ms · 70 KiBPolyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Minify CSS
150 ms · 8 KiB8 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
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: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.3 s
21.3 sYour largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “best sustainable candles”.
Time to Interactive: 22.6 s
22.6 sThe page becomes fully interactive after 22.6 s. Good is under 3.8 s.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 571 ms
571 msScripts block taps and scrolling for 571 ms in total while the page loads. Good is under 200 ms.
23 images without width and height
23 images have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.4 MB in 293 requests
6.4 MBYour homepage downloads 6.4 MB in 293 requests on a phone: images 2.4 MB (40), scripts 2.1 MB (116) and other files 770 KiB (105). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Home_Flower.svg weighs 945 KiB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (59 KiB) 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.
1 image below the first screen load straight away
1 image further down the page (59 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.81 g of CO₂e: 216.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
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.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (87 elements)
All page content should be contained by landmarks: 87 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (2 elements)
Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 13 failed. 3 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.
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Aerangis - Sustainable Scented Candles, Bespoke Luxury Home Fragrance”.
22 links with vague text
22 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
152 internal links, 6 external
The homepage links to 152 pages on aerangis.com and 6 external pages.
6 checks passed
Meta description: 75 characters
Your meta description is 75 characters: “Bespoke luxury scented candles - Documenting life's moments through scents.”.
Canonical URL set
The canonical URL is https://aerangis.com/.
Structured data in place
Structured data found: Organization 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://aerangis.com/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (789 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://aerangis.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://aerangis.com/collections and https://aerangis.com/collections/all all use the title “All products - Aerangis LLC”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://aerangis.com/collections/best-sellers, https://aerangis.com/collections/candle-care, https://aerangis.com/pages/bespoke, https://aerangis.com/blogs/journal and https://aerangis.com/pages/press2 have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://aerangis.com/collections and https://aerangis.com/collections/all use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://aerangis.com/collections/best-sellers/products/no-1-the-beginning, whose canonical is https://aerangis.com/products/no-1-the-beginning. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://aerangis.com/pages/bespoke has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
14 small tap targets
14 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Pasting is blocked
A form field blocks pasting, which frustrates password managers and people on phones.
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 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 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 1,283 words of copy
The homepage carries about 1,283 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
16 calls to action
The homepage has 16 calls to action, for example “Shop”, “Shop All” and “Sign up”.
23 short forms
23 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks, 5 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Meta Pixel and Pinterest Tag and 1 more (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
40 other companies contacted
Loading the homepage contacts 40 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 aerangis.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Helium Customer Fields · Go Gift Cards · Klaviyo Email Marketing Sms · Okendo · Hello World · chimpstatic.com · yotpo.com · printful.com · nfcube.com · prezenapps.com · gelato.tech · cloudfront.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
- The footer still says © 2022.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- New York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on aerangis.com, including 16 speed issues, 4 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.