Website review, no card needed
danielcassin.com.uy website review
Visit site (opens in a new tab)Reviewed 28 October 202640 issues · 83 checks
This review found 40 issues worth fixing on danielcassin.com.uy, 17 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 172 ms |
| May 16, 2026 | 175 ms |
| May 23, 2026 | 178 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 183 ms |
| Jun 13, 2026 | 184 ms |
| Jun 20, 2026 | 185 ms |
| Jun 27, 2026 | 189 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 199 ms |
| Jul 18, 2026 | 201 ms |
| Jul 25, 2026 | 202 ms |
| Aug 1, 2026 | 206 ms |
| Aug 8, 2026 | 213 ms |
| Aug 15, 2026 | 217 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 219 ms |
| Sep 5, 2026 | 217 ms |
| Sep 12, 2026 | 218 ms |
| Sep 19, 2026 | 217 ms |
| Sep 26, 2026 | 218 ms |
| Oct 3, 2026 | 216 ms |
| Oct 10, 2026 | 216 ms |
| Oct 17, 2026 | 217 ms |
| Oct 24, 2026 | 217 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
4.0 s · 794 KiBAbout 794 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
3.9 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.
Use efficient cache lifetimes
1.4 s · 367 KiB11 files are served with short cache lifetimes, so returning visitors download them again (367 KiB).
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 77). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
500 ms · 2.0 MB34 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, fcdn.app and Facebook and others), adding 4.1 MB and 1.7 s of main-thread time.
fcdn.app adds 453 ms
453 msfcdn.app costs a phone 453 ms of main-thread work and 2.6 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.
Google Tag Manager adds 531 ms
531 msGoogle Tag Manager costs a phone 531 ms of main-thread work and 747 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.
Facebook adds 353 ms
353 msFacebook costs a phone 353 ms of main-thread work and 374 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.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 261 ms. During a long task the page ignores taps.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Reduce unused CSS
150 ms · 49 KiBAbout 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 77 but mobile only 39. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 28 ms
28 msYour server sent the HTML in 28 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.
Largest Contentful Paint: 15.5 s
15.5 sYour largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Info cambios”.
Time to Interactive: 17.0 s
17.0 sThe page becomes fully interactive after 17.0 s. Good is under 3.8 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 946 ms
946 msScripts block taps and scrolling for 946 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 172 ms to 217 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 976 ms
976 msReal visitors wait 976 ms for your server to start answering (75th percentile). Good is under 800 ms.
20 images without width and height
20 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-10-24, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 184 ms
184 msReal visitors wait 184 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.2 MB in 112 requests
4.2 MBYour homepage downloads 4.2 MB in 112 requests on a phone: images 2.4 MB (61), scripts 1.6 MB (22) and fonts 85 KiB (2). Under 2 MB keeps phones on slow connections fast.
10 images far larger than shown
126 KiB10 images are downloaded at several times the size a phone draws them, for example homemedio-remeras-cassin.jpg at 1,000 px wide, shown at 317 px. Resized copies would save about 126 KiB.
2 images below the first screen load straight away
2 images further down the page (240 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 142.2 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
Unlabelled dropdowns
1 dropdown has no label.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (115 elements)
All page content should be contained by landmarks: 115 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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 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: “Daniel Cassin tienda online”. 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.
195 internal links, 10 external
The homepage links to 195 pages on danielcassin.com.uy and 10 external pages.
6 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Proponemos una mirada joven y fresca al diseño de vestimenta para la mujer urbana. Venta online y en nuestra red de loc…”.
One H1 headline
Your main headline reads: “Daniel Cassin”.
Canonical URL set
The canonical URL is https://www.danielcassin.com.uy/.
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://www.danielcassin.com.uy/sitemap.
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 (470 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.danielcassin.com.uy/llms.txt (3 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://www.danielcassin.com.uy/new-in, https://www.danielcassin.com.uy/vestimenta, https://www.danielcassin.com.uy/vestimenta/camisas-blusas, https://www.danielcassin.com.uy/vestimenta/pantalones-y-jeans, https://www.danielcassin.com.uy/remeras-y-musculosas and https://www.danielcassin.com.uy/vestimenta/abrigos/blazers and 8 others 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 98 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 “Failed to load resource: the server responded with a status of 404 (Not Found)”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
86 of 98 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 293 words of copy
The homepage carries about 293 words of visible text.
2 checks passed
20 short forms
20 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
25 other companies contacted
Loading the homepage contacts 25 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 danielcassin.com.uy, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Akamai Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on danielcassin.com.uy, including 20 speed issues, 2 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.