Website review, no card needed

luquibrinquedos.com.br logo

luquibrinquedos.com.br website review

Visit site (opens in a new tab)Reviewed 19 November 202623 issues · 77 checks

This review found 23 issues worth fixing on luquibrinquedos.com.br, 4 of them high impact, across 77 checks. The most urgent: 24 text elements with low contrast. 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

Full-page screenshot of luquibrinquedos.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. luquibrinquedos.com.br at 0.6 s0.6 s
  2. luquibrinquedos.com.br at 1.2 s1.2 s
  3. luquibrinquedos.com.br at 1.8 s1.8 s
  4. luquibrinquedos.com.br at 2.4 s2.4 s
  5. luquibrinquedos.com.br at 3.0 s3.0 s
  6. luquibrinquedos.com.br at 3.6 s3.6 s
  7. luquibrinquedos.com.br at 4.2 s4.2 s
  8. luquibrinquedos.com.br at 4.8 s4.8 s

Speed

2 to fix97
  • Render-blocking requests

    350 ms

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

  • Use efficient cache lifetimes

    298 KiB

    10 files are served with short cache lifetimes, so returning visitors download them again (298 KiB).

  • Improve image delivery

    211 KiB

    12 images could be 211 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Facebook, Cloudflare and on.aws and others), adding 523 KiB and 143 ms of main-thread time.

  • Minify JavaScript

    140 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    87 KiB

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

  • Legacy JavaScript

    21 KiB

    Polyfills for old browsers add 21 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 97

    97/100

    Your mobile performance score is 97. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

3 to fix100
  • Speed Index: 4.7 s

    4.7 s

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

  • 16 images without width and height

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

  • Time to Interactive: 4.1 s

    4.1 s

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

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

4 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.034

    0.034

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

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Pelúcias, jogos de tabuleiro, bonecas, Hot Wheels, Lego, Po…”.

  • Total Blocking Time: 33 ms

    33 ms

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    46 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo.png at 516 px wide, shown at 86 px. Resized copies would save about 46 KiB.

  • 2 images in older formats

    2 images (105 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.2 g of CO₂ per visit

    0.18 g

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

2 checks passed
  • Page weight: 643 KiB in 25 requests

    643 KiB

    Your homepage downloads 643 KiB in 25 requests on a phone: images 312 KiB (12), scripts 299 KiB (8) and HTML 26 KiB (1). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9494
  • 24 text elements with low contrast

    24 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 (161 elements)

    All page content should be contained by landmarks: 161 elements on the page fail this check, rated moderate by axe-core.

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

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

  • 3 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Luqui Brinquedos — Loja de brinquedos em Cascavel/PR | Entrega pra todo o Brasil”.

  • Meta description is long (225 characters)

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 294 internal links, 8 external

    The homepage links to 294 pages on luquibrinquedos.com.br and 8 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Loja de brinquedos em Cascavel/PR — com entrega pra todo o Brasil”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: ToyStore.

  • 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.luquibrinquedos.com.br/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.luquibrinquedos.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.

  • Opted out of AI training for 4 crawlers

    robots.txt blocks GPTBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

2 to fix93
  • 5 pages share a meta description

    https://www.luquibrinquedos.com.br/carrinho, https://www.luquibrinquedos.com.br/retirar-na-loja, https://www.luquibrinquedos.com.br/promocoes, https://www.luquibrinquedos.com.br/lista-aniversario and https://www.luquibrinquedos.com.br/produtos use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.luquibrinquedos.com.br/produtos 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 42 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

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

Best practices

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'open' of object '#<Window>'”.

2 checks passed
  • Tap targets are thumb-sized

    49 of 52 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix50
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

3 checks passed
  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel and Cloudflare Web Analytics.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta Pixel (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.

  • 2 cookies set on arrival

    2

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 luquibrinquedos.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

Hosting
Railway

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on luquibrinquedos.com.br, including 5 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