Website review, no card needed
aestheticeverything.com website review
Visit site (opens in a new tab)Reviewed 17 November 202642 issues · 87 checks
This review found 42 issues worth fixing on aestheticeverything.com, 17 of them high impact, across 87 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
68D- #102,513 of 116,487 reviewed websitesbeats 10%
- #62,294 of 66,776 online storesbeats 5%
- #2,245 of 2,670 WooCommerce storesbeats 13%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.2 s
2.3 s
3.5 s
4.6 s
5.8 s
6.9 s
8.1 s
9.2 s
Speed
Use efficient cache lifetimes
3.4 s · 1.2 MB107 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Improve image delivery
1.4 s · 2.8 MB11 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Reduce unused JavaScript
2.4 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.9 s44 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 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: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,014 HTML elements
The page has 3,014 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Maps and others), adding 2.2 MB and 1.1 s of main-thread time.
Google CDN adds 416 ms
416 msGoogle CDN costs a phone 416 ms of main-thread work and 742 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.
Reduce unused CSS
300 ms · 126 KiBAbout 126 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.
Google Tag Manager adds 275 ms
275 msGoogle Tag Manager costs a phone 275 ms of main-thread work and 404 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 Maps adds 178 ms
178 msGoogle Maps costs a phone 178 ms of main-thread work and 379 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.
Wufoo adds 66 ms
66 msWufoo costs a phone 66 ms of main-thread work and 424 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 233 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 255 ms
255 msYour server sent the HTML in 255 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 28.4 s
28.4 sYour largest element takes 28.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 32.0 s
32.0 sThe page becomes fully interactive after 32.0 s. Good is under 3.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 669 ms
669 msScripts block taps and scrolling for 669 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.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.
1 checks passed
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Images and page weight
Page weight: 9.8 MB in 262 requests
9.8 MBYour homepage downloads 9.8 MB in 262 requests on a phone: images 6.0 MB (123), scripts 2.4 MB (66) and fonts 715 KiB (12). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
188 KiB3 images are downloaded at several times the size a phone draws them, for example What-Is-Environ-768x990.jpg at 768 px wide, shown at 165 px. Resized copies would save about 188 KiB.
3 images below the first screen load straight away
3 images further down the page (322 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.8 g of CO₂ per visit
2.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.77 g of CO₂e: 332.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
58 tap targets too small
58 tap targets are too small or too close together to hit reliably with a finger.
53 text elements with low contrast
53 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (10 elements)
Elements must only use permitted ARIA attributes: 10 elements on the page fail this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (240 elements)
All page content should be contained by landmarks: 240 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.
2 form fields without a label
2 form fields have 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.
Headings skip levels
Headings skip levels (h1 → h4, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 30 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (27 characters)
Your title is only 27 characters: “Home - Aesthetic Everything”. Between 30 and 65 characters leaves room to say what you do and for whom.
4 H1 headlines
There are 4 <h1> headlines (“WEIGHT LOSS TELEMEDICINE CLINICIANS”, “SPEAKERS / INFLUENCERS” and “AWARDS NOMINEES”). One clear main headline is easier for people and search engines.
Meta description is long (366 characters)
Your meta description is 366 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
159 internal links, 17 external
The homepage links to 159 pages on aestheticeverything.com and 17 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://aestheticeverything.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://aestheticeverything.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (3,423 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://aestheticeverything.com/llms.txt (44 KiB, 179 links), a plain-text guide to the site for AI tools.
Other pages
5 pages share 2 titles
https://aestheticeverything.com/category/featured, https://aestheticeverything.com/category/plastic-surgery and https://aestheticeverything.com/category/dermatologist all use the title “Listings - Aesthetic Everything”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://aestheticeverything.com/listing/kerafactor, https://aestheticeverything.com/listing/giselle-villar, https://aestheticeverything.com/listing/eva-sztupka, https://aestheticeverything.com/listing/dr-giselle-villar and https://aestheticeverything.com/listing/dermaconcepts use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://aestheticeverything.com/category/featured, https://aestheticeverything.com/instagram-influencer-growth-campaigns, https://aestheticeverything.com/contact-us, https://aestheticeverything.com/vote-now, https://aestheticeverything.com/category/plastic-surgery and https://aestheticeverything.com/category/dermatologist have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://aestheticeverything.com/category/featured, https://aestheticeverything.com/contact-us, https://aestheticeverything.com/category/plastic-surgery and https://aestheticeverything.com/category/dermatologist have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://aestheticeverything.com/listing/eva-sztupka took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 83 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
5 broken images
5 images failed to load on a phone, for example https://aestheticeverything.com/wp-content/uploads/slider/cache/9ce50dcc048e6b6884a6cb6d80c70608/slider-weight-loss-scaled.jpg.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “[Splunk]: SplunkRum.init() - beaconEndpoint is required. SplunkRum will not be initialized.”.
2 checks passed
Tap targets are thumb-sized
46 of 52 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
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.
Thin social proof
Social proof on the homepage: 212 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 2,556 words of copy
The homepage carries about 2,556 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: “Contact” and “Join Now”.
10 calls to action
The homepage has 10 calls to action, for example “Contact”, “Join Now” and “JOIN NOW”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
15 other companies contacted
Loading the homepage contacts 15 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 aestheticeverything.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on aestheticeverything.com, including 18 speed issues, 4 SEO issues and 2 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.