Website review, no card needed

gruporedcarpet.es logo

gruporedcarpet.es website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 78 checks

This review found 32 issues worth fixing on gruporedcarpet.es, 9 of them high impact, across 78 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
4.6 s1.7 sJun 13Nov 143.9 s
Show as table
DateReal-visitor load time (LCP)
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Aug 15, 20262.4 s
Aug 22, 20262.7 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.7 s
Sep 26, 20262.3 s
Oct 24, 20263.9 s
Oct 31, 20264.2 s
Nov 7, 20264.2 s
Nov 14, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
136 ms103 msJun 20Nov 7110 ms
Show as table
DateReal-visitor tap response (INP)
Jun 20, 2026110 ms
Jun 27, 2026111 ms
Jul 4, 2026112 ms
Jul 11, 2026110 ms
Aug 15, 2026107 ms
Aug 29, 2026132 ms
Sep 5, 2026131 ms
Sep 12, 2026129 ms
Sep 19, 2026119 ms
Nov 7, 2026110 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 gruporedcarpet.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gruporedcarpet.es at 0.5 s0.5 s
  2. gruporedcarpet.es at 1.0 s1.0 s
  3. gruporedcarpet.es at 1.4 s1.4 s
  4. gruporedcarpet.es at 1.9 s1.9 s
  5. gruporedcarpet.es at 2.4 s2.4 s
  6. gruporedcarpet.es at 2.9 s2.9 s
  7. gruporedcarpet.es at 3.4 s3.4 s
  8. gruporedcarpet.es at 3.9 s3.9 s

Speed

7 to fix39
  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 39

    39/100

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

  • Improve image delivery

    900 ms · 245 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (nitrocdn.com, Google Tag Manager and Google Analytics and others), adding 1.9 MB and 828 ms of main-thread time.

  • Reduce unused JavaScript

    570 ms · 248 KiB

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

  • nitrocdn.com adds 597 ms

    597 ms

    nitrocdn.com costs a phone 597 ms of main-thread work and 1.6 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.

  • Reduce unused CSS

    460 ms · 97 KiB

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

  • Minify JavaScript

    160 ms · 42 KiB

    42 KiB could be saved by minifying JavaScript.

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 18 KiB

    Polyfills for old browsers add 18 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 CSS

    10 ms · 15 KiB

    15 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    16 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (16 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.8 s

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

  • Server response: 216 ms

    216 ms

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

Core Web Vitals

7 to fix36
  • Largest Contentful Paint: 8.5 s

    8.5 s

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

  • Cumulative Layout Shift: 0.642

    0.642

    The layout shifts by 0.642 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 13.3 s

    13.3 s

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

  • Speed Index: 7.7 s

    7.7 s

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

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

    +94%

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

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

1 checks passed
  • Total Blocking Time: 123 ms

    123 ms

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

Images and page weight

2 to fix78
  • Page weight: 2.8 MB in 84 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 84 requests on a phone: images 1.6 MB (25), scripts 691 KiB (32) and fonts 344 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

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

  • 8 images in older formats

    8 images (488 KiB) 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.

  • About 0.8 g of CO₂ per visit

    0.78 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.7 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 8190
  • 22 tap targets too small

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

  • 2 text elements with low contrast

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

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

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

  • 11 links without text

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

  • 1 form field without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 24 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 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

3 to fixGoogle 10085
  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Empresa de organización de eventos en Alicante. Red Carpet Grupo Red Carpet”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“DESCARGAS FOTOMATÓN” and “¿ Preparado para destacar ?”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 147 internal links, 7 external

    The homepage links to 147 pages on gruporedcarpet.es and 7 external pages.

5 checks passed
  • Meta description: 105 characters

    Your meta description is 105 characters: “Organización de todo tipo de eventos en Alicate y provincia. Calidad, seriedad y servicio nos distinguen.”.

  • Canonical URL set

    The canonical URL is https://www.gruporedcarpet.es/.

  • Structured data in place

    Structured data found: Article, Organization, Person, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.gruporedcarpet.es/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.gruporedcarpet.es/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 (837 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 3 pages without a meta description

    https://www.gruporedcarpet.es/servicios/event-carpet/eventos-de-empresa, https://www.gruporedcarpet.es/servicios/party-carpet/wedfest-bodas-alicante and https://www.gruporedcarpet.es/iluminacion-y-decoracion-para-bodas-en-alicante have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

    9 of 29 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 “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 604 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Audio Guest Book”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 8 cookies set on arrival

    8

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 gruporedcarpet.es, 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 32 issues on gruporedcarpet.es, including 14 speed issues, 3 SEO issues and 1 conversion gap. 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