Website review, no card needed

richst.com.br logo

richst.com.br website review

Visit site (opens in a new tab)Reviewed 16 November 202631 issues · 75 checks

This review found 31 issues worth fixing on richst.com.br, 10 of them high impact, across 75 checks. The most urgent: page weight: 4.5 MB in 243 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.2 s2.1 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20262.8 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.7 s
Aug 8, 20263.1 s
Aug 15, 20262.8 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.4 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Nov 7, 20262.6 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
139 ms100 msMay 30Sep 26128 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026112 ms
Jun 6, 2026111 ms
Jun 13, 2026104 ms
Sep 5, 2026134 ms
Sep 12, 2026134 ms
Sep 26, 2026128 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 richst.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. richst.com.br at 0.4 s0.4 s
  2. richst.com.br at 0.8 s0.8 s
  3. richst.com.br at 1.1 s1.1 s
  4. richst.com.br at 1.5 s1.5 s
  5. richst.com.br at 1.9 s1.9 s
  6. richst.com.br at 2.3 s2.3 s
  7. richst.com.br at 2.6 s2.6 s
  8. richst.com.br at 3.0 s3.0 s

Speed

7 to fix83
  • Mobile performance score: 83

    83/100

    Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    950 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

  • Reduce unused JavaScript

    577 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Shopify and Other Google APIs/SDKs and others), adding 1.2 MB and 430 ms of main-thread time.

  • YouTube adds 381 ms

    381 ms

    YouTube costs a phone 381 ms of main-thread work and 986 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 · 147 KiB

    About 147 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.

  • Main-thread work: 2.1 s

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

  • 4 long tasks on the main thread

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

  • Improve image delivery

    15 KiB

    1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    12 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (12 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: 8 ms

    8 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 13.1 s

    13.1 s

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

  • Largest Contentful Paint: 4.0 s

    4.0 s

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

  • Speed Index: 4.3 s

    4.3 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

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

    +17%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • 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 CLS: 0.00

    0.00

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

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Total Blocking Time: 145 ms

    145 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

1 to fix70
  • Page weight: 4.5 MB in 243 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 243 requests on a phone: media 1.6 MB (1), scripts 1.1 MB (80) and other files 839 KiB (124). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.28 g

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

5 to fixGoogle 8292
  • Hidden but focusable

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • 5 links without text

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

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • Title is short (18 characters)

    Your title is only 18 characters: “Início Rich Studio”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (22 characters)

    Your meta description is only 22 characters: “Peça já sua arte hoje!”. 70 to 160 characters is enough to sell the click.

  • 74 internal links, 2 external

    The homepage links to 74 pages on richst.com.br and 2 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Rich Studio”.

  • Canonical URL set

    The canonical URL is https://www.richst.com.br/.

  • Structured data in place

    Structured data found: Organization.

  • 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.richst.com.br/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing 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.

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

  • llms.txt published

    The site publishes https://www.richst.com.br/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.richst.com.br/pages/contact, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages without an H1

    https://www.richst.com.br/collections/loja, https://www.richst.com.br/collections/transforme-sua-ideia-em-arte, https://www.richst.com.br/blogs/rich-blog and https://www.richst.com.br/pages/contato have 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 27 found) and read each the way a search engine does.

5 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 14 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    21 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 180 words

    The homepage has only about 180 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.

1 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 4 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.

  • 20 other companies contacted

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

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Retentionly Whatsapp

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on richst.com.br, including 11 speed issues, 2 SEO issues and 6 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