Website review, no card needed

drimer.pe logo

drimer.pe website review

Visit site (opens in a new tab)Reviewed 19 October 202652 issues · 93 checks

This review found 52 issues worth fixing on drimer.pe, 19 of them high impact, across 93 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
4.6 s3.0 sApr 25Oct 104.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.1 s
May 2, 20263.3 s
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.5 s
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.7 s
Jun 20, 20263.8 s
Jun 27, 20264.0 s
Jul 4, 20264.1 s
Jul 11, 20264.0 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.8 s
Aug 8, 20264.0 s
Aug 15, 20264.2 s
Aug 22, 20264.3 s
Aug 29, 20264.4 s
Sep 5, 20264.4 s
Sep 12, 20264.4 s
Sep 19, 20264.4 s
Sep 26, 20264.4 s
Oct 3, 20264.4 s
Oct 10, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
273 ms208 msApr 25Oct 10227 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026265 ms
May 2, 2026263 ms
May 9, 2026258 ms
May 16, 2026257 ms
May 23, 2026249 ms
May 30, 2026236 ms
Jun 6, 2026226 ms
Jun 13, 2026221 ms
Jun 20, 2026221 ms
Jun 27, 2026219 ms
Jul 4, 2026218 ms
Jul 11, 2026219 ms
Jul 18, 2026222 ms
Jul 25, 2026226 ms
Aug 1, 2026225 ms
Aug 8, 2026227 ms
Aug 15, 2026218 ms
Aug 22, 2026215 ms
Aug 29, 2026216 ms
Sep 5, 2026221 ms
Sep 12, 2026229 ms
Sep 19, 2026231 ms
Sep 26, 2026237 ms
Oct 3, 2026233 ms
Oct 10, 2026227 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 drimer.pe (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drimer.pe at 0.8 s0.8 s
  2. drimer.pe at 1.7 s1.7 s
  3. drimer.pe at 2.5 s2.5 s
  4. drimer.pe at 3.3 s3.3 s
  5. drimer.pe at 4.1 s4.1 s
  6. drimer.pe at 5.0 s5.0 s
  7. drimer.pe at 5.8 s5.8 s
  8. drimer.pe at 6.6 s6.6 s

Speed

15 to fix21
  • Reduce unused JavaScript

    8.3 s · 1.5 MB

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

  • Use efficient cache lifetimes

    4.8 s · 1.1 MB

    44 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • vtexassets.com adds 1.1 s

    1.1 s

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

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 849 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: 21

    21/100

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

  • Main-thread work: 8.7 s

    A phone's processor spends 8.7 s on main-thread work while loading, 5.2 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 6.8 MB and 3.8 s of main-thread time.

  • Google CDN adds 980 ms

    980 ms

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

  • Minify JavaScript

    750 ms · 120 KiB

    120 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    450 ms · 150 KiB

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

  • Improve image delivery

    200 ms · 278 KiB

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    300 ms · 47 KiB

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

  • Facebook adds 279 ms

    279 ms

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

  • 2,791 HTML elements

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

  • Render-blocking requests

    150 ms

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

  • Font display

    100 ms

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

  • Minify CSS

    12 KiB

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

  • 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

14 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 LCP: 5.5 s

    5.5 s

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

  • Real-user CLS: 0.26

    0.26

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

  • First Contentful Paint: 19.4 s

    19.4 s

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

  • Largest Contentful Paint: 38.9 s

    38.9 s

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

  • Speed Index: 19.4 s

    19.4 s

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

  • Time to Interactive: 40.6 s

    40.6 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user INP: 206 ms

    206 ms

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

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

    +37%

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.18

    0.18

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

  • 11 images without width and height

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

1 checks passed
  • Tap response (INP) got 13% faster for real visitors

    -13%

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

Images and page weight

2 to fix60
  • Page weight: 7.6 MB in 185 requests

    7.6 MB

    Your homepage downloads 7.6 MB in 185 requests on a phone: scripts 3.6 MB (70), fonts 2.1 MB (17) and other files 733 KiB (51). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    22 KiB

    1 image is downloaded at several times the size a phone draws it, for example RECURSOS_DIFERENCIAL-LATEX.png at 915 px wide, shown at 276 px. Resized copies would save about 22 KiB.

  • 3 images in older formats

    3 images (308 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.

  • 3 images below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.14 g

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

Accessibility

8 to fixGoogle 8489
  • 2 buttons without a name

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

  • Hidden but focusable

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

  • 6 text elements with low contrast

    6 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 (4 elements)

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

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

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

  • 9 links without text

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

  • 2 form fields without a label

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

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

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

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

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

  • 38 internal links, 1 external

    The homepage links to 38 pages on drimer.pe and 1 external page.

6 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Explora colchones, camas y muebles de calidad que mejoran tu descanso y estilo de vida. Elige Drimer y compra online co…”.

  • One H1 headline

    Your main headline reads: “Descubre el diferencial de Drimer”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Tienda Online de Camas, Colchones, Muebles y más | Drimer”.

  • Canonical URL set

    The canonical URL is https://www.drimer.pe/.

  • 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.drimer.pe/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.

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

  • llms.txt published

    The site publishes https://www.drimer.pe/llms.txt (2 KiB, 10 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix74
  • 1 linked page hidden from search

    https://www.drimer.pe/sillones is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages share 2 titles

    https://www.drimer.pe/landing-beautyrest-simmons and https://www.drimer.pe/tiendas all use the title “Drimer | Tienda online, colchones, camas, dormitorios y más”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages share a meta description

    https://www.drimer.pe/landing-beautyrest-simmons, https://www.drimer.pe/tiendas, https://www.drimer.pe/dormitorio, https://www.drimer.pe/sillones, https://www.drimer.pe/camas-inteligentes and https://www.drimer.pe/sensoria-drimer use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.drimer.pe/dormitorio/almohadas, whose canonical is https://www.drimer.pe/almohadas. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://www.drimer.pe/ventas-corporativas, https://www.drimer.pe/sillones, https://www.drimer.pe/sensoria-drimer, https://www.drimer.pe/colchones-serta, https://www.drimer.pe/camas-serta and https://www.drimer.pe/almohadas-serta have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.drimer.pe/tiendas 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.

  • 7 pages slow to respond

    https://www.drimer.pe/landing-serta, https://www.drimer.pe/landing-beautyrest-simmons, https://www.drimer.pe/colchones, https://www.drimer.pe/camas, https://www.drimer.pe/dormitorio and https://www.drimer.pe/dormitorio/almohadas and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 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 a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 11 small tap targets

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

  • 3 JavaScript errors while loading

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

  • 3 distorted images

    3 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

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

  • Thin social proof

    Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 326 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Call center 01 - 7052299”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

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

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies (measured from a US location before any click).

  • 34 other companies contacted

    Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 drimer.pe, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on drimer.pe, including 29 speed issues, 2 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