Website review, no card needed

feirashop.com.br logo

feirashop.com.br website review

Visit site (opens in a new tab)Reviewed 4 November 202653 issues · 88 checks

This review found 53 issues worth fixing on feirashop.com.br, 18 of them high impact, across 88 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
2.7 s2.4 sMay 23Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.7 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
341 ms211 msMay 23Oct 31323 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026276 ms
May 30, 2026290 ms
Jun 6, 2026308 ms
Jun 13, 2026321 ms
Jun 20, 2026288 ms
Jun 27, 2026261 ms
Jul 4, 2026244 ms
Jul 11, 2026226 ms
Jul 18, 2026230 ms
Jul 25, 2026242 ms
Aug 1, 2026236 ms
Aug 8, 2026263 ms
Aug 15, 2026269 ms
Aug 22, 2026266 ms
Aug 29, 2026272 ms
Sep 5, 2026274 ms
Sep 12, 2026270 ms
Sep 19, 2026272 ms
Sep 26, 2026279 ms
Oct 3, 2026289 ms
Oct 10, 2026296 ms
Oct 17, 2026299 ms
Oct 24, 2026326 ms
Oct 31, 2026323 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 feirashop.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. feirashop.com.br at 0.7 s0.7 s
  2. feirashop.com.br at 1.4 s1.4 s
  3. feirashop.com.br at 2.1 s2.1 s
  4. feirashop.com.br at 2.8 s2.8 s
  5. feirashop.com.br at 3.4 s3.4 s
  6. feirashop.com.br at 4.1 s4.1 s
  7. feirashop.com.br at 4.8 s4.8 s
  8. feirashop.com.br at 5.5 s5.5 s

Speed

10 to fix52
  • Improve image delivery

    4.3 s · 8.5 MB

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

  • Use efficient cache lifetimes

    2.4 s · 8.2 MB

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

  • Reduce unused JavaScript

    2.3 s · 493 KiB

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

  • Mobile performance score: 52

    52/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and ContentSquare and others), adding 1.1 MB and 839 ms of main-thread time.

  • Google Tag Manager adds 435 ms

    435 ms

    Google Tag Manager costs a phone 435 ms of main-thread work and 544 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.

  • Render-blocking requests

    450 ms

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

  • Facebook adds 218 ms

    218 ms

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

  • Main-thread work: 2.4 s

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

  • 1,849 HTML elements

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

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    41 KiB

    Polyfills for old browsers add 41 KiB JavaScript that modern phones do not need.

  • 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: 1 ms

    1 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 31.6 s

    31.6 s

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

  • Time to Interactive: 35.0 s

    35.0 s

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

  • Speed Index: 14.8 s

    14.8 s

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

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 326 ms

    326 ms

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

  • Real-user TTFB: 812 ms

    812 ms

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

  • Total Blocking Time: 247 ms

    247 ms

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

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

    +15%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

3 checks passed
  • 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

6 to fix19
  • Page weight: 10.9 MB in 139 requests

    10.9 MB

    Your homepage downloads 10.9 MB in 139 requests on a phone: images 9.1 MB (63), scripts 1.6 MB (32) and other files 144 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 6.9 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    2.7 MB

    9 images are downloaded at several times the size a phone draws them, for example 09029b20-45d2-4efc-88a7-7e16cff9f72a.png at 1,524 px wide, shown at 82 px. Resized copies would save about 2.7 MB.

  • 22 images in older formats

    22 images (6.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.

  • 9 images below the first screen load straight away

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

  • An image on the first screen is lazy-loaded

    mobile.jpg 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).

  • About 3.1 g of CO₂ per visit

    3.10 g

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

Accessibility

11 to fixGoogle 9088
  • 50 text elements with low contrast

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

  • 3 tap targets too small

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

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

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

  • Alternative text of images should not be repeated as text (8 elements)

    Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

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

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

8 to fixGoogle 10059
  • No H1 headline

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

  • Title is short (28 characters)

    Your title is only 28 characters: “Lojas Digitais na Feira Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (65 characters)

    Your meta description is only 65 characters: “Moda, acessórios, eletrônicos, cosméticos, calçados e muito mais!”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

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

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

  • No XML sitemap

    No XML sitemap at https://feirashop.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at feirashop.com.br/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 14 internal links, 12 external

    The homepage links to 14 pages on feirashop.com.br and 12 external pages.

AI search readiness

2 to fix42
  • Most text only appears after JavaScript runs

    14%

    A phone browser shows 976 words, but the HTML your server sends has only 140. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

Other pages

2 to fix90
  • 9 pages share a title

    /, https://feirashop.com.br/ofertas, https://feirashop.com.br/quem-somos, https://feirashop.com.br/primavera, https://feirashop.com.br/produtos and https://feirashop.com.br/lojas and 3 others all use the title “Lojas Digitais na Feira Shop”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages share a meta description

    https://feirashop.com.br/ofertas, https://feirashop.com.br/quem-somos, https://feirashop.com.br/primavera, https://feirashop.com.br/produtos, https://feirashop.com.br/lojas and https://feirashop.com.br/politica-de-uso and 2 others use the same meta description. A description written for each page earns more clicks.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 10093
  • 34 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

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

    The homepage carries about 976 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Lojas Feira Shop”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 12 cookies set on arrival

    12

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 feirashop.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

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on feirashop.com.br, including 19 speed issues, 8 SEO issues and 3 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