Website review, no card needed

pacoperfumerias.com logo

pacoperfumerias.com website review

Visit site (opens in a new tab)Reviewed 22 October 202631 issues · 85 checks

This review found 31 issues worth fixing on pacoperfumerias.com, 14 of them high impact, across 85 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
1.7 s1.2 sMay 2Oct 171.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
231 ms166 msMay 2Oct 17216 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026173 ms
May 9, 2026173 ms
May 16, 2026177 ms
May 23, 2026177 ms
May 30, 2026179 ms
Jun 6, 2026186 ms
Jun 13, 2026189 ms
Jun 20, 2026193 ms
Jun 27, 2026195 ms
Jul 4, 2026196 ms
Jul 11, 2026199 ms
Jul 18, 2026199 ms
Jul 25, 2026201 ms
Aug 1, 2026203 ms
Aug 8, 2026208 ms
Aug 15, 2026216 ms
Aug 22, 2026221 ms
Aug 29, 2026223 ms
Sep 5, 2026220 ms
Sep 12, 2026219 ms
Sep 19, 2026218 ms
Sep 26, 2026217 ms
Oct 3, 2026218 ms
Oct 10, 2026216 ms
Oct 17, 2026216 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 pacoperfumerias.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pacoperfumerias.com at 0.6 s0.6 s
  2. pacoperfumerias.com at 1.3 s1.3 s
  3. pacoperfumerias.com at 1.9 s1.9 s
  4. pacoperfumerias.com at 2.5 s2.5 s
  5. pacoperfumerias.com at 3.1 s3.1 s
  6. pacoperfumerias.com at 3.8 s3.8 s
  7. pacoperfumerias.com at 4.4 s4.4 s
  8. pacoperfumerias.com at 5.0 s5.0 s

Speed

10 to fix55
  • Reduce unused JavaScript

    2.2 s · 444 KiB

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

  • Improve image delivery

    1.2 s · 328 KiB

    15 images could be 328 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • 4,620 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, consentmanager.net and Salesforce Commerce Cloud and others), adding 1.0 MB and 1.2 s of main-thread time.

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 61). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    800 ms

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

  • Google Tag Manager adds 698 ms

    698 ms

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

    650 ms · 126 KiB

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

  • consentmanager.net adds 355 ms

    355 ms

    consentmanager.net costs a phone 355 ms of main-thread work and 149 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: 2.6 s

    A phone's processor spends 2.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused CSS

    150 ms · 63 KiB

    About 63 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

    150 ms · 30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 11 long tasks on the main thread

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

  • 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: 70 ms

    70 ms

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

Core Web Vitals

9 to fix67
  • 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: 13.5 s

    13.5 s

    Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DESCUENTO EXTRA PACO PERFUMERIAS”.

  • Time to Interactive: 13.8 s

    13.8 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • Real-user INP: 221 ms

    221 ms

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

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

    +25%

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

  • 27 images without width and height

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

  • Total Blocking Time: 316 ms

    316 ms

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

6 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 586 ms

    586 ms

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix78
  • Page weight: 2.0 MB in 90 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 90 requests on a phone: scripts 1.1 MB (30), images 641 KiB (35) and HTML 132 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (56 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.6 g of CO₂ per visit

    0.58 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8392
  • 11 buttons without a name

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

  • 73 text elements with low contrast

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

  • 11 tap targets too small

    11 tap targets are too small or too close together to hit reliably with a finger.

  • Links look like plain text

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

  • 5 links without text

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

2 checks passed
  • Every image has alt text

    All 74 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

Google 100100
  • 572 internal links, 9 external

    The homepage links to 572 pages on pacoperfumerias.com and 9 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Paco Perfumerías, con más de 30 años ofreciendo: Perfumes, Maquillaje, Cosmética y Parafarmacia. En nuestra perfumería …”.

  • One H1 headline

    Your main headline reads: “Tienda de perfumería, maquillaje y cosmética online”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Tienda de perfumes y cosmética · Mejor Precio - Paco Perfumerías”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness, Organization, WebPage 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://www.pacoperfumerias.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.pacoperfumerias.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,520 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://www.pacoperfumerias.com/joyeria-y-bisuteria and https://www.pacoperfumerias.com/gafas-de-sol use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://www.pacoperfumerias.com/perfumes, https://www.pacoperfumerias.com/perfumes-mujer, https://www.pacoperfumerias.com/perfumes-hombre and https://www.pacoperfumerias.com/perfumes-baratos have 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 199 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

Google 96100
  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    48 of 52 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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.

  • Thin social proof

    Social proof on the homepage: 24 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 1,494 words of copy

    The homepage carries about 1,494 words of visible text.

5 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 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). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • 13 other companies contacted

    Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: consentmanager

    A consent management tool (consentmanager) 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 pacoperfumerias.com, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on pacoperfumerias.com, including 19 speed 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

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