Website review, no card needed
daniello.com website review
Visit site (opens in a new tab)Reviewed 5 November 202635 issues · 85 checks
This review found 35 issues worth fixing on daniello.com, 12 of them high impact, across 85 checks. The most urgent: page weight: 5.7 MB in 300 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
80B- #46,289 of 117,615 reviewed websitesbeats 55%
- #30,852 of 66,923 online storesbeats 47%
- #29,686 of 61,018 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 97 ms |
| May 23, 2026 | 102 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 107 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 106 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 114 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 125 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 130 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 123 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
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.5 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 CDN, iubenda and Shopify and others), adding 2.8 MB and 1.7 s of main-thread time.
Reduce unused JavaScript
1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Google CDN adds 718 ms
718 msGoogle CDN costs a phone 718 ms of main-thread work and 1.4 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.
iubenda adds 557 ms
557 msiubenda costs a phone 557 ms of main-thread work and 125 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
350 ms · 115 KiB5 images could be 115 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Render-blocking requests
350 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
2,164 HTML elements
The page has 2,164 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 130 ms
130 msShopify costs a phone 130 ms of main-thread work and 594 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.
Use efficient cache lifetimes
150 ms · 71 KiB12 files are served with short cache lifetimes, so returning visitors download them again (71 KiB).
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 170 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
45 KiBAbout 45 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 28.5 s
28.5 sThe page becomes fully interactive after 28.5 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 97 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 529 ms
529 msScripts block taps and scrolling for 529 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 123 ms
123 msReal visitors wait 123 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 569 ms
569 msReal visitors wait 569 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 300 requests
5.7 MBYour homepage downloads 5.7 MB in 300 requests on a phone: scripts 2.9 MB (109), other files 1.5 MB (137) and images 759 KiB (20). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 193.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
7 dropdowns have no label.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
9 form fields without a label
9 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 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 31 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (28 characters)
Your title is only 28 characters: “D'Aniello.com – Daniello.com”. Between 30 and 65 characters leaves room to say what you do and for whom.
One H1 headline
Your <h1> is empty.
209 internal links, 3 external
The homepage links to 209 pages on daniello.com and 3 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://daniello.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://daniello.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description 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 (1,452 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://daniello.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://daniello.com/collections/new-arrivals-for-you, which answers with an error. Visitors hit a dead end and search engines drop it.
12 pages without a meta description
https://daniello.com/collections/woman, https://daniello.com/collections/women-clothing, https://daniello.com/collections/women-swimwear, https://daniello.com/collections/women-blazers, https://daniello.com/collections/women-coat and https://daniello.com/collections/women-dresses and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://daniello.com/collections/woman 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 103 found) and read each the way a search engine does.
4 checks passed
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 14 pages that loaded have a <title>.
Best practices
27 small tap targets
27 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 1,214 words of copy
The homepage carries about 1,214 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “SUBSCRIBE”.
10 calls to action
The homepage has 10 calls to action, for example “SHOP NOW”, “shop now” and “SHOP THEB BRAND”.
3 short forms
3 short forms (6 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
34 other companies contacted
Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) 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 daniello.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Forms · Digital Appointments · Bookeasy · Back In Stock · webmarked.net · amazonaws.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
- Tailwind CSS
- 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 35 issues on daniello.com, including 16 speed issues, 3 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.