Website review, no card needed

destinofnails.com logo

destinofnails.com website review

Visit site (opens in a new tab)Reviewed 18 November 202625 issues · 73 checks

This review found 25 issues worth fixing on destinofnails.com, 11 of them high impact, across 73 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

Full-page screenshot of destinofnails.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix68
  • Reduce unused JavaScript

    4.0 s · 426 KiB

    About 426 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.

  • Mobile performance score: 68

    68/100

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

  • Render-blocking requests

    900 ms

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

  • Improve image delivery

    150 ms · 652 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.3 MB and 482 ms of main-thread time.

  • Google CDN adds 294 ms

    294 ms

    Google CDN costs a phone 294 ms of main-thread work and 742 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

    130 ms · 68 KiB

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

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    76 KiB

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

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

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 12.9 s

    12.9 s

    Your largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CENTRO DE ESTÉTICA EN MAJADAHONDA destino of nails CONTACTO”.

  • Time to Interactive: 13.4 s

    13.4 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s on a phone. Good is under 1.8 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: 91 ms

    91 ms

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

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

1 to fix70
  • Page weight: 6.4 MB in 76 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 76 requests on a phone: images 4.8 MB (46), scripts 991 KiB (10) and other files 356 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (35 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.

  • 5 images below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.82 g

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

7 to fixGoogle 8690
  • 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.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 92 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.

  • 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
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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
  • 22 internal links, 23 external

    The homepage links to 22 pages on destinofnails.com and 23 external pages.

8 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “Centro de estética en Majadahonda. Ofrecemos tratamientos de manicura, pedicura, masajes y mucho más. Todos pensados pa…”.

  • One H1 headline

    Your main headline reads: “CENTRO DE ESTÉTICA EN MAJADAHONDA”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Centro de estética en Majadahonda | Destino of Nails”.

  • Canonical URL set

    The canonical URL is https://destinofnails.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://destinofnails.com/sitemap_index.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.

  • No llms.txt

    There is no https://destinofnails.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.

2 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,293 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix90
  • 1 page points its canonical at the homepage

    https://destinofnails.com/bonos declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 1 page with very little text

    https://destinofnails.com/contacto has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 8 pages slow to respond

    https://destinofnails.com/manicura-majadahonda, https://destinofnails.com/pedicura-en-majadahonda, https://destinofnails.com/depilacion-en-majadahonda, https://destinofnails.com/masajes-en-majadahonda, https://destinofnails.com/cejas-y-pestanas-en-majadahonda and https://destinofnails.com/tratamientos-de-cabina and 2 others took over 3 s to send their HTML from our server.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Every page has a meta description

    All 9 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed
  • 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.

  • Local business without LocalBusiness data

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

  • No opening hours

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

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

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

5 checks passed
  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 35 testimonial or review blocks and 48 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

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

  • 2 cookies set on arrival

    2

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 destinofnails.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Combell NV

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on destinofnails.com, including 10 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