Website review, no card needed
aprilskin.us website review
Visit site (opens in a new tab)Reviewed 13 November 202642 issues · 91 checks
This review found 42 issues worth fixing on aprilskin.us, 10 of them high impact, across 91 checks. The most urgent: page weight: 58.0 MB in 357 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
82B- #30,886 of 108,859 reviewed websitesbeats 66%
- #20,614 of 61,765 online storesbeats 60%
- #19,944 of 56,365 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 136 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 156 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 184 ms |
| Aug 1, 2026 | 166 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 136 ms |
| Sep 12, 2026 | 130 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 126 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 117 ms |
| Oct 31, 2026 | 113 ms |
| Nov 7, 2026 | 110 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.2 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Accessibe Accessibility Overlay and JSDelivr CDN and others), adding 54.2 MB and 463 ms of main-thread time.
Shopify adds 143 ms
143 msShopify costs a phone 143 ms of main-thread work and 53.5 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.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
450 ms · 484 KiB13 images could be 484 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused JavaScript
150 ms · 387 KiBAbout 387 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,595 HTML elements
The page has 1,595 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
160 KiB23 files are served with short cache lifetimes, so returning visitors download them again (160 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 102 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).
Reduce unused CSS
30 KiBAbout 30 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
7 KiB7 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
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
Largest Contentful Paint: 10.4 s
10.4 sYour largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A.C.E Serum”.
Time to Interactive: 20.2 s
20.2 sThe page becomes fully interactive after 20.2 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.204
0.204The layout shifts by 0.204 while loading, so content jumps under the reader's thumb. Good is under 0.1.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 784 ms
784 msReal visitors wait 784 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 136 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 32 ms
32 msScripts block the page for only 32 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 58.0 MB in 357 requests
58.0 MBYour homepage downloads 58.0 MB in 357 requests on a phone: media 52.3 MB (4), images 1.9 MB (40) and fonts 1.3 MB (13). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (3.9 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.
5 images below the first screen load straight away
5 images further down the page (3.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
125 KiB2 images are downloaded at several times the size a phone draws them, for example US_AP_main_BnA_img_4_86af4161-bd6d-4bd7-b883-e145953533a3.we at 1,600 px wide, shown at 390 px. Resized copies would save about 125 KiB.
About 16.4 g of CO₂ per visit
16.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 16.44 g of CO₂e: 1972.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
5 dropdowns have no label.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (15 elements)
ARIA role should be appropriate for the element: 15 elements on the page fail this check, rated minor by axe-core.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 H1 headlines
There are 6 <h1> headlines (“”, “CARROTENE IPMP™” and “Calendula”). One clear main headline is easier for people and search engines.
Meta description is long (219 characters)
Your meta description is 219 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
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.
138 internal links, 3 external
The homepage links to 138 pages on aprilskin.us and 3 external pages.
6 checks passed
Title: 47 characters
Your title is a healthy 47 characters: “APRILSKIN US | High-performance gentle skincare”.
Canonical URL set
The canonical URL is https://aprilskin.us/.
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://aprilskin.us/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 (976 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://aprilskin.us/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 pages without a meta description
https://aprilskin.us/collections/all-products, https://aprilskin.us/collections/skin-concerns-enlarged-pores, https://aprilskin.us/collections/wrinkles-uneven-tone, https://aprilskin.us/collections/redness-sensitivity, https://aprilskin.us/collections/face-wash-cleansers and https://aprilskin.us/collections/toners-facial-pads and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://aprilskin.us/collections/a-c-e 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 55 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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 53 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 13 testimonial or review blocks. 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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 559 words of copy
The homepage carries about 559 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
14 calls to action
The homepage has 14 calls to action, for example “SHOP”, “SHOP ALL” and “Contact Us”.
16 short forms
16 short forms (2 fields at most) are right on the homepage.
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
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Snap 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.
32 other companies contacted
Loading the homepage contacts 32 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 aprilskin.us, 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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Wisepops Popup Builder Cro · Upcart · Freegifts · pxucdn.com · affilo.io · orderlogicapp.com · jsdelivr.net · amazonaws.com · chimpstatic.com · snapchat.com · bogos.io · hextom.com · edgecdnplus.com
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
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
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 aprilskin.us, including 13 speed issues, 5 SEO issues and 3 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.