Website review, no card needed

editorarideel.com.br logo

editorarideel.com.br website review

Visit site (opens in a new tab)Reviewed 3 November 202651 issues · 89 checks

This review found 51 issues worth fixing on editorarideel.com.br, 18 of them high impact, across 89 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
3.8 s3.5 sMay 16Oct 313.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.7 s
May 23, 20263.7 s
May 30, 20263.7 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.6 s
Jul 11, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.6 s
Sep 26, 20263.5 s
Oct 3, 20263.6 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
268 ms191 msMay 16Oct 31226 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026201 ms
May 23, 2026203 ms
May 30, 2026204 ms
Jun 6, 2026209 ms
Jun 13, 2026219 ms
Jun 20, 2026222 ms
Jun 27, 2026213 ms
Jul 4, 2026206 ms
Jul 11, 2026203 ms
Jul 18, 2026200 ms
Jul 25, 2026207 ms
Aug 1, 2026214 ms
Aug 8, 2026212 ms
Aug 15, 2026217 ms
Aug 22, 2026217 ms
Aug 29, 2026221 ms
Sep 5, 2026227 ms
Sep 12, 2026234 ms
Sep 19, 2026240 ms
Sep 26, 2026244 ms
Oct 3, 2026250 ms
Oct 10, 2026259 ms
Oct 17, 2026247 ms
Oct 24, 2026233 ms
Oct 31, 2026226 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 editorarideel.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. editorarideel.com.br at 1.1 s1.1 s
  2. editorarideel.com.br at 2.2 s2.2 s
  3. editorarideel.com.br at 3.4 s3.4 s
  4. editorarideel.com.br at 4.5 s4.5 s
  5. editorarideel.com.br at 5.6 s5.6 s
  6. editorarideel.com.br at 6.7 s6.7 s
  7. editorarideel.com.br at 7.8 s7.8 s
  8. editorarideel.com.br at 9.0 s9.0 s

Speed

10 to fix49
  • Render-blocking requests

    2.0 s

    26 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 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.

  • Main-thread work: 9.0 s

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

  • 8,185 HTML elements

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

  • Improve image delivery

    150 ms · 8.3 MB

    8 images could be 8.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    740 ms · 132 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Unpkg and others), adding 1.3 MB and 513 ms of main-thread time.

  • Reduce unused JavaScript

    630 KiB

    About 630 KiB of JavaScript is downloaded but never used on this page.

  • Google CDN adds 355 ms

    355 ms

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

  • Font display

    400 ms

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

  • Minify JavaScript

    150 ms · 202 KiB

    202 KiB could be saved by minifying JavaScript.

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    83 KiB

    9 files are served with short cache lifetimes, so returning visitors download them again (83 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.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

11 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 INP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 22.1 s

    22.1 s

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

  • Speed Index: 16.6 s

    16.6 s

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

  • Time to Interactive: 41.1 s

    41.1 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Total Blocking Time: 443 ms

    443 ms

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

  • 11 images without width and height

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

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

2 checks passed
  • Real-user CLS: 0.06

    0.06

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

  • 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 fix45
  • Page weight: 12.4 MB in 439 requests

    12.4 MB

    Your homepage downloads 12.4 MB in 439 requests on a phone: images 9.4 MB (81), scripts 2.0 MB (284) and other files 404 KiB (36). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Mini_Banner_LER_GIF_Black.gif weighs 6.8 MB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (6.8 MB) 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.

  • An image on the first screen is lazy-loaded

    Logo_Rideel-Digital_AZUL_1.png 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 below the first screen load straight away

    1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.5 g of CO₂ per visit

    3.51 g

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

10 to fixGoogle 7089
  • 124 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • Orphan list items

    Some list items are not inside a list.

  • 7 links without text

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

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

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

2 checks passed
  • Every image has alt text

    All 139 images in the HTML carry an alt attribute.

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

SEO

7 to fixGoogle 9266
  • No H1 headline

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

  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “Editora Rideel | Black Friday - Livros Acadêmicos, Jurídicos, Concurso e OAB”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (249 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links crawlers can't follow

    4 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 incomplete here.

  • 367 internal links, 11 external

    The homepage links to 367 pages on editorarideel.com.br and 11 external pages.

2 checks passed
  • 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.editorarideel.com.br/media/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.editorarideel.com.br/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 (3,205 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix62
  • 2 linked pages are broken

    Your homepage links to https://www.editorarideel.com.br/vade-2024-segundo-semestre and https://www.editorarideel.com.br/promoc-o-do-dia-66154bcbcf957, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    https://www.editorarideel.com.br/lancamento/vade-mecuns-2024 and https://www.editorarideel.com.br/lancamento/ultimos-lancamentos-rideel all use the title “Últimos Lançamentos | Livros Atualizados Editora Rideel”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.editorarideel.com.br/lancamento/vade-mecuns-2024 and https://www.editorarideel.com.br/lancamento/ultimos-lancamentos-rideel use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.editorarideel.com.br/vade-mecum-academico-2026-2 has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 10 small tap targets

    10 of 33 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: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 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 1,951 words of copy

    The homepage carries about 1,951 words of visible text.

4 checks passed
  • 73 short forms

    73 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 142 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 16 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 editorarideel.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Magento
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 51 issues on editorarideel.com.br, including 21 speed issues, 7 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