Website review, no card needed
alastin.com website review
Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 91 checks
This review found 44 issues worth fixing on alastin.com, 15 of them high impact, across 91 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
76C- #73,327 of 120,337 reviewed websitesbeats 34%
- #47,209 of 68,137 online storesbeats 26%
- #44,772 of 62,092 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.1 s |
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 131 ms |
| May 2, 2026 | 136 ms |
| May 9, 2026 | 140 ms |
| May 16, 2026 | 145 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 144 ms |
| Jun 13, 2026 | 140 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 150 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 169 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 169 ms |
| Oct 10, 2026 | 164 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.9 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Reduce unused CSS
1.1 s · 205 KiBAbout 205 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 49
49/100Your mobile performance score is 49 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,702 HTML elements
The page has 3,702 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 Tag Manager, heatmap.com and Listrak and others), adding 1.9 MB and 1.0 s of main-thread time.
Use efficient cache lifetimes
300 ms · 811 KiB150 files are served with short cache lifetimes, so returning visitors download them again (811 KiB).
Reduce unused JavaScript
696 KiBAbout 696 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
150 ms · 365 KiB23 images could be 365 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 304 ms. During a long task the page ignores taps.
Google Tag Manager adds 245 ms
245 msGoogle Tag Manager costs a phone 245 ms of main-thread work and 353 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.
Listrak adds 120 ms
120 msListrak costs a phone 120 ms of main-thread work and 582 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.
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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: 28.0 s
28.0 sThe page becomes fully interactive after 28.0 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.8 s
5.8 sYour largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 131 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 372 ms
372 msScripts block taps and scrolling for 372 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.136
0.136The layout shifts by 0.136 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 562 ms
562 msReal visitors wait 562 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 5.2 MB in 531 requests
5.2 MBYour homepage downloads 5.2 MB in 531 requests on a phone: scripts 2.2 MB (223), other files 1.5 MB (194) and images 1.3 MB (85). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Mobile_Homepage_Hero_750x600_26026_Opt2_no_text.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.5 g of CO₂ per visit
1.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 177.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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”.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
48 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: 48 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “ALASTIN Skincare | Anti-Aging & Treatment Enhancing Skincare | Alastin USA”.
3 H1 headlines
There are 3 <h1> headlines (“REGENERATIVE SKINCARE ON A WHOLE OTHER LEVEL”, “Regenerative skincare on a whole other level” and “Regenerative skincare on a whole other level”). One clear main headline is easier for people and search engines.
21 links with vague text
21 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Meta description is long (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
140 internal links, 16 external
The homepage links to 140 pages on alastin.com and 16 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://alastin.com/.
Structured data in place
Structured data found: BreadcrumbList, LocalBusiness, 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://alastin.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,479 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://alastin.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://alastin.com/collections/all and https://alastin.com/collections/best-sellers have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 74 found) and read each the way a search engine does.
6 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.
Every page has an H1
Each page we checked has a main headline.
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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
40 of 46 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 3 trust badges. 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.
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 1,066 words of copy
The homepage carries about 1,066 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP THE GIFT GUIDE”.
20 calls to action
The homepage has 20 calls to action, for example “Shop Skincare expand”, “Back Shop Skincare” and “Subscribe & Save”.
9 short forms
9 short forms (4 fields at most) are right on the homepage, asking for an email.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
41 cookies set on arrival
41Opening the homepage sets 41 cookies (measured from a US location before any click).
72 other companies contacted
Loading the homepage contacts 72 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 alastin.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- 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 44 issues on alastin.com, including 22 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.