Website review, no card needed

cristaljoyas.com logo

cristaljoyas.com website review

Visit site (opens in a new tab)Reviewed 24 October 202655 issues · 89 checks

This review found 55 issues worth fixing on cristaljoyas.com, 23 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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
3.9 s2.0 sMay 2Oct 173.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.6 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20263.0 s
Sep 5, 20263.3 s
Sep 12, 20263.5 s
Sep 19, 20263.7 s
Sep 26, 20263.6 s
Oct 3, 20263.5 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
105 ms90 msMay 2Oct 17103 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202695 ms
May 9, 202694 ms
May 16, 202693 ms
May 23, 202693 ms
May 30, 202692 ms
Jun 6, 202693 ms
Jun 13, 202694 ms
Jun 20, 202693 ms
Jun 27, 202694 ms
Jul 4, 202694 ms
Jul 11, 202694 ms
Jul 18, 202694 ms
Jul 25, 202694 ms
Aug 1, 202694 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202696 ms
Aug 29, 202697 ms
Sep 5, 202697 ms
Sep 12, 202699 ms
Sep 19, 2026101 ms
Sep 26, 2026102 ms
Oct 3, 2026103 ms
Oct 10, 2026103 ms
Oct 17, 2026103 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 cristaljoyas.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cristaljoyas.com at 0.5 s0.5 s
  2. cristaljoyas.com at 1.0 s1.0 s
  3. cristaljoyas.com at 1.5 s1.5 s
  4. cristaljoyas.com at 2.0 s2.0 s
  5. cristaljoyas.com at 2.5 s2.5 s
  6. cristaljoyas.com at 3.0 s3.0 s
  7. cristaljoyas.com at 3.5 s3.5 s
  8. cristaljoyas.com at 4.0 s4.0 s

Speed

10 to fix40
  • Render-blocking requests

    5.2 s

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

  • Reduce unused JavaScript

    3.7 s · 645 KiB

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

  • Improve image delivery

    1.8 s · 1.4 MB

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

  • Use efficient cache lifetimes

    1.9 s · 261 KiB

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

  • Minify JavaScript

    1.4 s · 279 KiB

    279 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 40

    40/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Facebook and others), adding 1.4 MB and 1.1 s of main-thread time.

  • Google Tag Manager adds 444 ms

    444 ms

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

  • ZenDesk adds 343 ms

    343 ms

    ZenDesk costs a phone 343 ms of main-thread work and 474 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.2 s

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

  • 9 long tasks on the main thread

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

  • Font display

    200 ms

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

  • Reduce unused CSS

    150 ms · 37 KiB

    About 37 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 · 17 KiB

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

  • Minify CSS

    11 KiB

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

10 to fix100
  • 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.

  • First Contentful Paint: 8.7 s

    8.7 s

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

  • Largest Contentful Paint: 26.9 s

    26.9 s

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

  • Time to Interactive: 31.1 s

    31.1 s

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

  • Speed Index: 14.8 s

    14.8 s

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

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

    +33%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 874 ms

    874 ms

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

  • Total Blocking Time: 512 ms

    512 ms

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

  • 15 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 116 ms

    116 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.09

    0.09

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

Images and page weight

4 to fix43
  • Page weight: 4.8 MB in 344 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 344 requests on a phone: scripts 2.1 MB (263), images 1.9 MB (23) and fonts 619 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (1.5 MB) are 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.

  • 8 images below the first screen load straight away

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

  • 4 images far larger than shown

    455 KiB

    4 images are downloaded at several times the size a phone draws them, for example Banner_Principal___Home_1920x764.jpg at 1,920 px wide, shown at 392 px. Resized copies would save about 455 KiB.

  • About 1.4 g of CO₂ per visit

    1.37 g

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

Accessibility

10 to fixGoogle 7786
  • 27 text elements with low contrast

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

  • 2 tap targets too small

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

  • Malformed lists

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

  • 3 buttons without a name

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

  • 1 image without alt text

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

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

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

  • 22 links without text

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 8358
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

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

  • Title is short (13 characters)

    Your title is only 13 characters: “Cristal Joyas”. 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.

  • Meta description is short (13 characters)

    Your meta description is only 13 characters: “Cristal Joyas”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • 3 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 83 internal links, 5 external

    The homepage links to 83 pages on cristaljoyas.com and 5 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://cristaljoyas.com/sitemap.xml.

AI search readiness

2 to fix37
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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://cristaljoyas.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Other pages

3 to fix86
  • 2 pages share a title

    https://cristaljoyas.com/anillos-de-compromiso.html and https://cristaljoyas.com/anillos-de-compromiso/anillos-de-compromiso.html all use the title “Anillos de Compromiso - CRISTAL JOYAS”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://cristaljoyas.com/anillos-de-compromiso.html and https://cristaljoyas.com/anillos-de-compromiso/anillos-de-compromiso.html use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://cristaljoyas.com/anillos-de-compromiso/guia-diamante-autentico.html has 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 64 found) and read each the way a search engine does.

5 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 14 pages that loaded have a meta description.

  • 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

3 to fixGoogle 7385
  • 9 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 82 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 19 cookies set on arrival

    19

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

  • 18 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on cristaljoyas.com, including 20 speed issues, 8 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