Website review, no card needed
altalavrenti.com website review
Visit site (opens in a new tab)Reviewed 11 November 202639 issues · 81 checks
This review found 39 issues worth fixing on altalavrenti.com, 15 of them high impact, across 81 checks. The most urgent: avoid multiple page redirects. 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
77C- #70,000 of 126,428 reviewed websitesbeats 39%
- #44,934 of 70,467 online storesbeats 31%
- #42,682 of 63,959 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
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
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.8 s
3.4 s
4.1 s
4.8 s
5.5 s
Speed
Avoid multiple page redirects
7.2 sThe page goes through 1 redirect before it starts loading, costing about 7.2 s. Link and advertise the final URL directly.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,497 HTML elements
The page has 3,497 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
740 ms · 163 KiBAbout 163 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 740 ms faster on a phone.
Improve image delivery
517 KiB15 images could be 517 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
5 third-party services on the page
5 third-party services load with your homepage (Shopify, Google CDN and shop.app and others), adding 2.1 MB and 250 ms of main-thread time.
Shopify adds 226 ms
226 msShopify costs a phone 226 ms of main-thread work and 764 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.
judgeme.com adds 0 ms
0 msjudgeme.com costs a phone 0 ms of main-thread work and 1.2 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
Render-blocking requests
50 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 50 ms.
Use efficient cache lifetimes
17 KiB6 files are served with short cache lifetimes, so returning visitors download them again (17 KiB).
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
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
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.7 s
16.7 sYour largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 17.1 s
17.1 sThe page becomes fully interactive after 17.1 s. Good is under 3.8 s.
Speed Index: 6.3 s
6.3 sVisually, the page fills in at 6.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
14 images without width and height
14 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.
3 checks passed
Largest content (LCP) got 32% faster for real visitors
-32%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.4 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 101 ms
101 msScripts block the page for only 101 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.7 MB in 381 requests
6.7 MBYour homepage downloads 6.7 MB in 381 requests on a phone: images 4.0 MB (72), other files 1.3 MB (124) and scripts 1,015 KiB (157). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
7D59D1EE-38C8-42F5-B3B3-C34AD7001868_copy.jpg 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.9 g of CO₂ per visit
1.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.89 g of CO₂e: 227.1 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
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
58 text elements with low contrast
58 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
4 elements hidden from screen readers can still receive keyboard focus.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (352 elements)
All page content should be contained by landmarks: 352 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.
1 form field without a label
1 form field has 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
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (13 characters)
Your title is only 13 characters: “Âlta Lavrenti”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (22 characters)
Your meta description is only 22 characters: “Fashion at new heights”. 70 to 160 characters is enough to sell the click.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
78 internal links, 30 external
The homepage links to 78 pages on altalavrenti.com and 30 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Âlta LavrentiÂlta Lavrenti”.
Canonical URL set
The canonical URL is https://altalavrenti.com/.
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://altalavrenti.com/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.
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 (2,699 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://altalavrenti.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://altalavrenti.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://altalavrenti.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
6 pages without a meta description
https://altalavrenti.com/collections/all-collections, https://altalavrenti.com/pages/contact, https://altalavrenti.com/pages/happy-customers, https://altalavrenti.com/customer_authentication/redirect, https://altalavrenti.com/collections/ss23 and https://altalavrenti.com/collections/neutrals have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://altalavrenti.com/collections/all-collections, https://altalavrenti.com/pages/contact, https://altalavrenti.com/pages/happy-customers and https://altalavrenti.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://altalavrenti.com/customer_authentication/redirect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 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.
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.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
24 of 28 tappable elements near the top are at least 24 px.
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 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 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 3,236 words of copy
The homepage carries about 3,236 words of visible text.
3 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “Subscribe icon-right-arrow” and “Shop Now”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 133 testimonial or review blocks and a star rating.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, 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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 1 of them by other companies (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.
24 other companies contacted
Loading the homepage contacts 24 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 altalavrenti.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Judge Me Reviews · Auction Today · Currency Converter
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
- 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 39 issues on altalavrenti.com, including 14 speed issues, 4 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.