Website review, no card needed

florsol.es logo

florsol.es website review

Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 79 checks

This review found 43 issues worth fixing on florsol.es, 15 of them high impact, across 79 checks. The most urgent: 1 button without a name. 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

Full-page screenshot of florsol.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. florsol.es at 0.4 s0.4 s
  2. florsol.es at 0.8 s0.8 s
  3. florsol.es at 1.1 s1.1 s
  4. florsol.es at 1.5 s1.5 s
  5. florsol.es at 1.9 s1.9 s
  6. florsol.es at 2.3 s2.3 s
  7. florsol.es at 2.6 s2.6 s
  8. florsol.es at 3.0 s3.0 s

Speed

6 to fix62
  • Improve image delivery

    900 ms · 1,008 KiB

    18 images could be 1,008 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 286 KiB

    About 286 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Render-blocking requests

    500 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

  • Google Tag Manager adds 404 ms

    404 ms

    Google Tag Manager costs a phone 404 ms of main-thread work and 519 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.

  • Reduce unused CSS

    300 ms · 61 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, pxucdn.com and Shopify and others), adding 924 KiB and 445 ms of main-thread time.

  • Font display

    250 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

  • 3 long tasks on the main thread

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

  • Minify CSS

    20 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Use efficient cache lifetimes

    4 KiB

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

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 543 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix52
  • Largest Contentful Paint: 9.1 s

    9.1 s

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

  • Time to Interactive: 12.8 s

    12.8 s

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

  • Cumulative Layout Shift: 0.203

    0.203

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

  • 21 images without width and height

    21 images have no width and height attributes, so the layout jumps as each one loads.

  • Speed Index: 3.9 s

    3.9 s

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

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

2 checks passed
  • Total Blocking Time: 165 ms

    165 ms

    Scripts block the page for only 165 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

Images and page weight

3 to fix58
  • 10 images far larger than shown

    638 KiB

    10 images are downloaded at several times the size a phone draws them, for example 6_970e640d-3ac4-4263-a8b3-9846ea5b1535_800x.jpg at 800 px wide, shown at 150 px. Resized copies would save about 638 KiB.

  • Page weight: 3.2 MB in 169 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 169 requests on a phone: images 1.3 MB (28), scripts 861 KiB (42) and other files 856 KiB (85). Under 2 MB keeps phones on slow connections fast.

  • 10 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (52 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.9 g of CO₂ per visit

    0.91 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.91 g of CO₂e: 108.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

11 to fixGoogle 6482
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (54 elements)

    All page content should be contained by landmarks: 54 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 12 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 7775
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 55 internal links, 0 external

    The homepage links to 55 pages on florsol.es and 0 external pages.

4 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Florsol|Tienda de compras integral - florsol”.

  • Canonical URL set

    The canonical URL is https://www.florsol.es/.

  • 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.florsol.es/sitemap.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 (302 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

6 to fix52
  • 1 linked page is broken

    Your homepage links to https://www.florsol.es/collections/ropa-de-damas, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://www.florsol.es/collections/joyas/products/pendientes-de-pavo-real-1 and https://www.florsol.es/collections/joyas/products/pendientes-de-pavo-real all use the title “Pendientes de pavo real – florsol”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://www.florsol.es/collections, https://www.florsol.es/collections/ropa-y-accesorios, https://www.florsol.es/collections/ropa-interior-y-pijamas, https://www.florsol.es/collections/chaqueta, https://www.florsol.es/collections/falda and https://www.florsol.es/collections/bolsa-y-accesorios and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.florsol.es/collections/joyas/products/pendientes-de-pavo-real-1 and https://www.florsol.es/collections/joyas/products/pendientes-de-pavo-real use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.florsol.es/collections/joyas/products/pendientes-de-pavo-real-1, whose canonical is https://www.florsol.es/products/pendientes-de-pavo-real-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.florsol.es/collections/joyas/products/pendientes-de-pavo-real-1, https://www.florsol.es/collections/joyas/products/anillo-de-descompresion-elegante-1 and https://www.florsol.es/collections/joyas/products/pendientes-de-pavo-real have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.florsol.es/collections/falda, https://www.florsol.es/collections/bolsa-y-accesorios and https://www.florsol.es/collections/bolsas took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • 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

1 to fixGoogle 9693
  • 12 small tap targets

    12 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

  • Only about 211 words

    The homepage has only about 211 words of visible text; thin pages give Google and first-time buyers little to go on.

3 checks passed
  • 15 short forms

    15 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 8 cookies set on arrival

    8

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 florsol.es, 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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

pxucdn.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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on florsol.es, including 11 speed issues, 4 SEO issues and 5 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