Website review, no card needed

rickysarkany.com logo

rickysarkany.com website review

Visit site (opens in a new tab)Reviewed 2 November 202656 issues · 95 checks

This review found 56 issues worth fixing on rickysarkany.com, 26 of them high impact, across 95 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
6.6 s2.7 sMay 16Oct 313.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.5 s
May 23, 20265.4 s
May 30, 20265.4 s
Jun 6, 20265.5 s
Jun 13, 20265.7 s
Jun 20, 20265.6 s
Jun 27, 20265.7 s
Jul 4, 20265.8 s
Jul 11, 20266.0 s
Jul 18, 20266.1 s
Jul 25, 20266.1 s
Aug 1, 20266.0 s
Aug 8, 20265.5 s
Aug 15, 20265.3 s
Aug 22, 20265.2 s
Aug 29, 20264.8 s
Sep 5, 20264.4 s
Sep 12, 20263.9 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Oct 17, 20263.4 s
Oct 24, 20263.4 s
Oct 31, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
423 ms327 msMay 16Oct 31338 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026361 ms
May 23, 2026357 ms
May 30, 2026353 ms
Jun 6, 2026339 ms
Jun 13, 2026338 ms
Jun 20, 2026352 ms
Jun 27, 2026371 ms
Jul 4, 2026384 ms
Jul 11, 2026387 ms
Jul 18, 2026385 ms
Jul 25, 2026384 ms
Aug 1, 2026382 ms
Aug 8, 2026372 ms
Aug 15, 2026371 ms
Aug 22, 2026365 ms
Aug 29, 2026377 ms
Sep 5, 2026382 ms
Sep 12, 2026390 ms
Sep 19, 2026412 ms
Sep 26, 2026398 ms
Oct 3, 2026411 ms
Oct 10, 2026407 ms
Oct 17, 2026392 ms
Oct 24, 2026392 ms
Oct 31, 2026338 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 rickysarkany.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rickysarkany.com at 1.1 s1.1 s
  2. rickysarkany.com at 2.2 s2.2 s
  3. rickysarkany.com at 3.3 s3.3 s
  4. rickysarkany.com at 4.4 s4.4 s
  5. rickysarkany.com at 5.5 s5.5 s
  6. rickysarkany.com at 6.6 s6.6 s
  7. rickysarkany.com at 7.7 s7.7 s
  8. rickysarkany.com at 8.8 s8.8 s

Speed

13 to fix29
  • Reduce unused JavaScript

    3.0 s · 1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • Use efficient cache lifetimes

    3.6 s · 966 KiB

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

  • Improve image delivery

    2.8 s · 1.1 MB

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

  • vtexassets.com adds 1.3 s

    1.3 s

    vtexassets.com costs a phone 1.3 s of main-thread work and 2.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 1,016 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 8.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Google CDN and others), adding 5.9 MB and 3.7 s of main-thread time.

  • Reduce unused CSS

    610 ms · 162 KiB

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

  • Google CDN adds 480 ms

    480 ms

    Google CDN costs a phone 480 ms of main-thread work and 2.0 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.

  • Render-blocking requests

    450 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

  • 20 long tasks on the main thread

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

  • 1,658 HTML elements

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

  • Legacy JavaScript

    200 ms · 74 KiB

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

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

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

    18 ms

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

Core Web Vitals

12 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 CLS: 0.80

    0.80

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

  • Largest Contentful Paint: 20.6 s

    20.6 s

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

  • Time to Interactive: 32.5 s

    32.5 s

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

  • Speed Index: 14.9 s

    14.9 s

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

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user INP: 392 ms

    392 ms

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

2 checks passed
  • Largest content (LCP) got 41% faster for real visitors

    -41%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

4 to fix36
  • Page weight: 5.5 MB in 195 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 195 requests on a phone: scripts 3.1 MB (85), images 1.2 MB (29) and fonts 475 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    c08ff6b5-dcba-4762-82a0-8aace82d7196___ebc27e065f7cc73bb8992 weighs 695 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    201d330a-e35d-4f33-b971-96f2a4f6e25b___1574d4bf2b1c8cea81fdc is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (695 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 1.6 g of CO₂ per visit

    1.55 g

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

12 to fixGoogle 7683
  • Images must have alternative text (10 elements)

    Images must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.

  • 7 buttons without a name

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

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

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • 1 tap target too small

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (5 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 5 elements on the page fail this check, rated moderate by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

3 to fixGoogle 9288
  • Meta description is long (163 characters)

    Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (ItemList, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 6 internal links, 2 external

    The homepage links to 6 pages on rickysarkany.com and 2 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Ricky Sarkany”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Ricky Sarkany | Sitio Oficial, Compra Online y en Cuotas.”.

  • Canonical URL set

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

  • 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.rickysarkany.com/sitemap.xml.

AI search readiness

2 to fix58
  • Most text only appears after JavaScript runs

    22%

    A phone browser shows 296 words, but the HTML your server sends has only 64. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

2 checks passed
  • Organization data: 6 of 6 facts

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

  • llms.txt published

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

Other pages

3 to fix75
  • 1 page without a title

    https://www.rickysarkany.com/todos-los-productos has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://www.rickysarkany.com/todos-los-productos has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.rickysarkany.com/todos-los-productos has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.rickysarkany.com/sucursales 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.

  • 2 internal pages checked

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

4 checks passed
  • Linked pages load

    All 2 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

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

Best practices

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97174056&tm=gtm002&Ver=2&mid=7ec0f1fb-ec5f-43ee-bf09-946bb4c63830&bo=1&sid=13cbfcc0d70c11f1bc559511d444faaa&vid=13cc2b40d70c11f1825d41e8d04b7d86&vids=1&msclkid=N&gtm_t.

  • 44 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot set property $globalConfig of #<Ci> which has only a getter”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

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

  • About 296 words of copy

    The homepage carries about 296 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 1 call to action

    The homepage has 1 call to action, for example “Shop Worldwide”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 25 cookies set on arrival

    25

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

  • 50 other companies contacted

    Loading the homepage contacts 50 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 rickysarkany.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
React
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 56 issues on rickysarkany.com, including 25 speed issues, 3 SEO issues and 2 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