Website review, no card needed

cipitria.com.ar logo

cipitria.com.ar website review

Visit site (opens in a new tab)Reviewed 7 November 202642 issues · 88 checks

This review found 42 issues worth fixing on cipitria.com.ar, 15 of them high impact, across 88 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
6.4 s1.1 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20263.8 s
Jul 4, 20265.3 s
Jul 11, 20265.7 s
Jul 18, 20265.7 s
Jul 25, 20265.8 s
Aug 1, 20265.3 s
Aug 8, 20264.9 s
Aug 15, 20264.8 s
Aug 22, 20264.7 s
Aug 29, 20264.6 s
Sep 5, 20262.4 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.3 s
Oct 3, 20262.4 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
401 ms66 msMay 16Oct 31211 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026105 ms
May 23, 2026122 ms
May 30, 2026154 ms
Jun 6, 2026154 ms
Jun 13, 2026166 ms
Jun 20, 2026166 ms
Jun 27, 2026209 ms
Jul 4, 2026315 ms
Jul 11, 2026327 ms
Jul 18, 2026331 ms
Jul 25, 2026353 ms
Aug 1, 2026346 ms
Aug 8, 2026362 ms
Aug 15, 2026362 ms
Aug 22, 2026348 ms
Aug 29, 2026346 ms
Sep 5, 2026195 ms
Sep 12, 2026219 ms
Sep 19, 2026229 ms
Sep 26, 2026270 ms
Oct 3, 2026263 ms
Oct 10, 2026237 ms
Oct 17, 2026236 ms
Oct 24, 2026206 ms
Oct 31, 2026211 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 cipitria.com.ar (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cipitria.com.ar at 0.8 s0.8 s
  2. cipitria.com.ar at 1.7 s1.7 s
  3. cipitria.com.ar at 2.5 s2.5 s
  4. cipitria.com.ar at 3.4 s3.4 s
  5. cipitria.com.ar at 4.2 s4.2 s
  6. cipitria.com.ar at 5.0 s5.0 s
  7. cipitria.com.ar at 5.9 s5.9 s
  8. cipitria.com.ar at 6.7 s6.7 s

Speed

10 to fix49
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49. 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 (Facebook, Google Tag Manager and tiendanube.com and others), adding 2.0 MB and 1.0 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 697 KiB

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

  • Improve image delivery

    585 KiB

    5 images could be 585 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    150 ms · 320 KiB

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

  • 2,982 HTML elements

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

  • Main-thread work: 2.8 s

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

  • Google Tag Manager adds 181 ms

    181 ms

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

  • mitiendanube.com adds 86 ms

    86 ms

    mitiendanube.com costs a phone 86 ms of main-thread work and 967 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

    160 ms · 44 KiB

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

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    53 KiB

    Polyfills for old browsers add 53 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    30 KiB

    30 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    17 KiB

    17 KiB JavaScript is shipped twice across bundles.

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

    59 ms

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

Core Web Vitals

12 to fix33
  • 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.44

    0.44

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

  • Time to Interactive: 22.1 s

    22.1 s

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

  • First Contentful Paint: 6.4 s

    6.4 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Al navegar por este sitio aceptás el uso de cookies para ag…”.

  • Real-user INP: 203 ms

    203 ms

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

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

    +84%

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

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

    +40%

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

  • Real-user TTFB: 876 ms

    876 ms

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

  • Total Blocking Time: 400 ms

    400 ms

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

  • 12 images without width and height

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

3 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 87 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 87 requests on a phone: scripts 1.3 MB (35), images 877 KiB (11) and HTML 875 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.89 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 9088
  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

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

  • 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 (59 elements)

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

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

  • 54 form fields without a label

    54 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 links without text

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

  • Headings skip levels

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 68 links crawlers can't follow

    68 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 set, so this is minor.

  • 129 internal links, 0 external

    The homepage links to 129 pages on cipitria.com.ar and 0 external pages.

8 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Descubrí nuestra coleccion de trajes de baño, bikinis, pijamas y ropa interior de diseño. Prendas comodas y con estilo.…”.

  • One H1 headline

    Your main headline reads: “Cipitria - Bikinis, Pijamas y Ropa de Dormir para mujer”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Cipitria - Bikinis, Pijamas y Ropa de Dormir para mujer”.

  • Canonical URL set

    The canonical URL is https://www.cipitria.com.ar/.

  • Structured data in place

    Structured data found: Product and WebPage.

  • 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.cipitria.com.ar/sitemap.xml.gz.

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

  • llms.txt published

    The site publishes https://cipitria.com.ar/llms.txt (1 KiB, 1 link), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without an H1

    https://cipitria.com.ar/cybercipitria, https://cipitria.com.ar/cybercipitria/pijamas-amt5h, https://cipitria.com.ar/cybercipitria/pijamas-amt5h/pijamas-cyber-exclusivo, https://cipitria.com.ar/cybercipitria/trajes-de-bano-mxzkj, https://cipitria.com.ar/cybercipitria/trajes-de-bano-mxzkj/bikinis-1tpnm and https://cipitria.com.ar/cybercipitria/trajes-de-bano-mxzkj/enterizas-1hhqg and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://cipitria.com.ar/cybercipitria, https://cipitria.com.ar/cybercipitria/pijamas-amt5h, https://cipitria.com.ar/cybercipitria/pijamas-amt5h/pijamas-cyber-exclusivo and https://cipitria.com.ar/cybercipitria/trajes-de-bano-mxzkj took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 36 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

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://cipitria.com.ar/.

  • 51 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d2az8otjr0j19j.cloudfront.net/templates/007/239/302/twig/static/css/global_critica…”.

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.

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

    The homepage carries about 919 words of visible text.

2 checks passed
  • 52 short forms

    52 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 of them by other companies (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.

  • 26 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify;Shopify Local Pickup;Shopify Plus
Analytics
Google Analytics | Google Tag Manager
Hosting
As273584 Linked Store Brasil Criacao E Desenvol De Software

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on cipitria.com.ar, including 22 speed issues, 1 SEO issue 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