Website review, no card needed

crecos.com logo

crecos.com website review

Visit site (opens in a new tab)Reviewed 4 November 202660 issues · 96 checks

This review found 60 issues worth fixing on crecos.com, 28 of them high impact, across 96 checks. The most urgent: improve image delivery. 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
4.0 s3.7 sMay 16Oct 313.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.9 s
May 23, 20263.9 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20263.8 s
Jun 20, 20263.7 s
Jun 27, 20263.8 s
Jul 4, 20263.8 s
Jul 11, 20263.8 s
Jul 18, 20263.8 s
Jul 25, 20263.8 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.7 s
Oct 31, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
500 ms319 msMay 16Oct 31443 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026355 ms
May 23, 2026349 ms
May 30, 2026340 ms
Jun 6, 2026351 ms
Jun 13, 2026380 ms
Jun 20, 2026411 ms
Jun 27, 2026416 ms
Jul 4, 2026415 ms
Jul 11, 2026403 ms
Jul 18, 2026396 ms
Jul 25, 2026396 ms
Aug 1, 2026384 ms
Aug 8, 2026377 ms
Aug 15, 2026373 ms
Aug 22, 2026375 ms
Aug 29, 2026397 ms
Sep 5, 2026411 ms
Sep 12, 2026431 ms
Sep 19, 2026467 ms
Sep 26, 2026479 ms
Oct 3, 2026479 ms
Oct 10, 2026474 ms
Oct 17, 2026475 ms
Oct 24, 2026459 ms
Oct 31, 2026443 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 crecos.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crecos.com at 1.9 s1.9 s
  2. crecos.com at 3.9 s3.9 s
  3. crecos.com at 5.8 s5.8 s
  4. crecos.com at 7.8 s7.8 s
  5. crecos.com at 9.7 s9.7 s
  6. crecos.com at 11.7 s11.7 s
  7. crecos.com at 13.6 s13.6 s
  8. crecos.com at 15.6 s15.6 s

Speed

14 to fix29
  • Improve image delivery

    3.0 s · 2.6 MB

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

  • vtexassets.com adds 4.2 s

    4.2 s

    vtexassets.com costs a phone 4.2 s of main-thread work and 4.5 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.

  • Use efficient cache lifetimes

    1.8 s · 409 KiB

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

  • Google Tag Manager adds 1.9 s

    1.9 s

    Google Tag Manager costs a phone 1.9 s of main-thread work and 558 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.

  • Reduce unused JavaScript

    1.2 s · 521 KiB

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

  • Main-thread work: 16.7 s

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

  • Render-blocking requests

    1.3 s

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

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

  • 8 third-party services on the page

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

  • 20 long tasks on the main thread

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

  • Facebook adds 488 ms

    488 ms

    Facebook costs a phone 488 ms of main-thread work and 304 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.

  • TikTok adds 420 ms

    420 ms

    TikTok costs a phone 420 ms of main-thread work and 156 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

    300 ms · 63 KiB

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

  • 1,602 HTML elements

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

  • Legacy JavaScript

    150 ms · 57 KiB

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

  • Font display

    50 ms

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

  • Minify JavaScript

    7 KiB

    7 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: 43 ms

    43 ms

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

Core Web Vitals

13 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 INP: 616 ms

    616 ms

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

  • Real-user CLS: 0.39

    0.39

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

  • Largest Contentful Paint: 19.9 s

    19.9 s

    Your largest element takes 19.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: 30.9 s

    30.9 s

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

  • Speed Index: 13.0 s

    13.0 s

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

  • Total Blocking Time: 3.1 s

    3.1 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

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

    +28%

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

  • Real-user FCP: 2.2 s

    2.2 s

    Real visitors see the first content after 2.2 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.

  • 10 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

1 checks passed
  • Cumulative Layout Shift: 0.014

    0.014

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

Images and page weight

5 to fix18
  • Page weight: 6.1 MB in 180 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 180 requests on a phone: images 3.3 MB (59), scripts 1.9 MB (50) and fonts 461 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    571 KiB

    9 images are downloaded at several times the size a phone draws them, for example d4b5c35c-e907-4912-8fe4-cbf365ddb9a5___ca3bff06be160ecd58fb5 at 1,000 px wide, shown at 167 px. Resized copies would save about 571 KiB.

  • 5 images in older formats

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

  • 15 images below the first screen load straight away

    15 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.73 g

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

Accessibility

10 to fixGoogle 7685
  • 7 buttons without a name

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

  • 53 text elements with low contrast

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

  • 38 tap targets too small

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

    All page content should be contained by landmarks: 8 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 (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.

  • 23 links without text

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

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

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

2 checks passed
  • Every image has alt text

    All 89 images in the HTML carry an alt attribute.

  • 39 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: 39 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10076
  • No H1 headline

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

  • Title is short (29 characters)

    Your title is only 29 characters: “CRECOS es Créditos Económicos”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (ItemList 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.

  • 96 internal links, 14 external

    The homepage links to 96 pages on crecos.com and 14 external pages.

4 checks passed
  • Meta description: 107 characters

    Your meta description is 107 characters: “Ofertas en electrodomésticos, tecnología, audio, video, motos , scooter eléctricas y mas de 10000 artículos”.

  • Canonical URL set

    The canonical URL is https://www.crecos.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.crecos.com/sitemap.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://www.crecos.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 (366 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79
  • 2 linked pages hidden from search

    https://www.crecos.com/155 and https://www.crecos.com/205 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a title

    /, https://www.crecos.com/tiendas and https://www.crecos.com/entrega-prime all use the title “CRECOS es Créditos Económicos”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://www.crecos.com/tiendas, https://www.crecos.com/155, https://www.crecos.com/entrega-prime and https://www.crecos.com/205 use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.crecos.com/Motos, whose canonical is https://www.crecos.com/motos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages with very little text

    https://www.crecos.com/tiendas and https://www.crecos.com/entrega-prime have 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.

  • 6 pages slow to respond

    https://www.crecos.com/consolas-de-video-juego, https://www.crecos.com/electrodomesticos/aires-acondicionados, https://www.crecos.com/155, https://www.crecos.com/205, https://www.crecos.com/audio and https://www.crecos.com/Motos took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 26 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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.

  • Only about 222 words

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

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

  • Urgency cues

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

2 checks passed
  • 1 short form

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

  • Analytics in place

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 20 cookies set on arrival

    20

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 crecos.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
Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 60 issues on crecos.com, including 27 speed issues, 4 SEO issues and 5 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