Website review, no card needed

casanovafoto.com logo

casanovafoto.com website review

Visit site (opens in a new tab)Reviewed 23 October 202650 issues · 93 checks

This review found 50 issues worth fixing on casanovafoto.com, 21 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.4 s2.2 sMay 2Oct 173.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.8 s
Jun 13, 20263.1 s
Jun 20, 20263.5 s
Jun 27, 20263.8 s
Jul 4, 20264.2 s
Jul 11, 20264.2 s
Jul 18, 20263.9 s
Jul 25, 20263.6 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20263.3 s
Aug 22, 20263.5 s
Aug 29, 20263.8 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
296 ms173 msMay 2Oct 17282 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026188 ms
May 9, 2026188 ms
May 16, 2026187 ms
May 23, 2026187 ms
May 30, 2026194 ms
Jun 6, 2026198 ms
Jun 13, 2026200 ms
Jun 20, 2026202 ms
Jun 27, 2026196 ms
Jul 4, 2026193 ms
Jul 11, 2026194 ms
Jul 18, 2026196 ms
Jul 25, 2026198 ms
Aug 1, 2026200 ms
Aug 8, 2026203 ms
Aug 15, 2026204 ms
Aug 22, 2026209 ms
Aug 29, 2026214 ms
Sep 5, 2026220 ms
Sep 12, 2026221 ms
Sep 19, 2026223 ms
Sep 26, 2026236 ms
Oct 3, 2026253 ms
Oct 10, 2026263 ms
Oct 17, 2026282 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

Full-page screenshot of casanovafoto.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. casanovafoto.com at 1.0 s1.0 s
  2. casanovafoto.com at 1.9 s1.9 s
  3. casanovafoto.com at 2.9 s2.9 s
  4. casanovafoto.com at 3.9 s3.9 s
  5. casanovafoto.com at 4.9 s4.9 s
  6. casanovafoto.com at 5.8 s5.8 s
  7. casanovafoto.com at 6.8 s6.8 s
  8. casanovafoto.com at 7.8 s7.8 s

Speed

10 to fix44
  • Reduce unused JavaScript

    3.5 s · 838 KiB

    About 838 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

  • Render-blocking requests

    4.2 s

    49 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 5,517 HTML elements

    The page has 5,517 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 6 third-party services on the page

    6 third-party services load with your homepage (b-cdn.net, Google Tag Manager and Cookie-Script.com and others), adding 2.6 MB and 1.1 s of main-thread time.

  • Use efficient cache lifetimes

    900 ms · 235 KiB

    144 files are served with short cache lifetimes, so returning visitors download them again (235 KiB).

  • Reduce unused CSS

    760 ms · 239 KiB

    About 239 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.

  • b-cdn.net adds 670 ms

    670 ms

    b-cdn.net costs a phone 670 ms of main-thread work and 1.9 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 409 ms

    409 ms

    Google Tag Manager costs a phone 409 ms of main-thread work and 657 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.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Improve image delivery

    197 KiB

    20 images could be 197 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 189 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 274 ms

    274 ms

    Your server sent the HTML in 274 ms, well inside Google's 600 ms guideline.

Core Web Vitals

14 to fix0
  • 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.

  • Real-user LCP: 4.3 s

    4.3 s

    Real visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.1 s

    3.1 s

    Real visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.7 s

    2.7 s

    Real visitors wait 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 16.3 s

    16.3 s

    Your largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 16.9 s

    16.9 s

    The page becomes fully interactive after 16.9 s. Good is under 3.8 s.

  • Speed Index: 10.0 s

    10.0 s

    Visually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 3.8 s

    3.8 s

    The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

  • Real-user INP: 277 ms

    277 ms

    Real visitors wait 277 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.11

    0.11

    For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 45% slower for real visitors

    +45%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 188 ms to 282 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 53% slower for real visitors

    +53%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.186

    0.186

    The layout shifts by 0.186 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 275 ms

    275 ms

    Scripts block taps and scrolling for 275 ms in total while the page loads. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.8 MB in 173 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 173 requests on a phone: scripts 1.0 MB (40), images 634 KiB (49) and fonts 391 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

    4 images further down the page (160 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.79 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 95.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

7 to fixGoogle 8892
  • 33 buttons without a name

    33 buttons have no accessible name, so screen readers announce just “button”.

  • 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.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (8 elements)

    ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (8 elements)

    Elements marked as presentational should be consistently ignored: 8 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 103 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 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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

5 to fixGoogle 8573
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (19 characters)

    Your title is only 19 characters: “Home Page - Español”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 8 H1 headlines

    There are 8 <h1> headlines (“¡Nuevos cursos para 2026!”, “¡Llega la nueva OM SYSTEM PEN!” and “BONO CULTURAL JOVEN”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 577 internal links, 14 external

    The homepage links to 577 pages on casanovafoto.com and 14 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.casanovafoto.com/.

  • Structured data in place

    Structured data found: ElectronicsStore and SiteNavigationElement.

  • 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.casanovafoto.com/media/sitemap_es.xml.

AI search readiness

1 to fix88
  • 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,029 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.casanovafoto.com/llms.txt (6 KiB, 50 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix55
  • 1 linked page is broken

    Your homepage links to https://www.casanovafoto.com/fotografia/material-de-estudio, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://www.casanovafoto.com/catalogsearch/advanced is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages share a title

    https://www.casanovafoto.com/fotografia/camaras, https://www.casanovafoto.com/fotografia/camaras/nikon and https://www.casanovafoto.com/fotografia/camaras/fujifilm all use the title “Cámaras fotográficas - Para profesionales y principiantes - Casanova …”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.casanovafoto.com/catalogsearch/advanced has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.casanovafoto.com/fotografia/camaras, https://www.casanovafoto.com/fotografia/camaras/nikon and https://www.casanovafoto.com/fotografia/camaras/fujifilm use the same meta description. A description written for each page earns more clicks.

  • 4 pages slow to respond

    https://www.casanovafoto.com/fotografia, https://www.casanovafoto.com/fotografia/camaras, https://www.casanovafoto.com/fotografia/camaras/nikon and https://www.casanovafoto.com/fotografia/camaras/fujifilm took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 188 found) and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9282
  • 10 broken images

    10 images failed to load on a phone, for example https://www.casanovafoto.com/.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    63 of 68 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix61
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • 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 818 words of copy

    The homepage carries about 818 words of visible text.

5 checks passed
  • 43 short forms

    43 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 casanovafoto.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
Bootstrap
E-commerce
Magento
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on casanovafoto.com, including 24 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25