Website review, no card needed

niazi.com.br logo

niazi.com.br website review

Visit site (opens in a new tab)Reviewed 26 October 202643 issues · 82 checks

This review found 43 issues worth fixing on niazi.com.br, 17 of them high impact, across 82 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 s4.0 sMay 9Oct 244.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.5 s
May 16, 20264.4 s
May 23, 20264.3 s
May 30, 20264.1 s
Jun 6, 20264.1 s
Jun 13, 20264.1 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.3 s
Jul 11, 20264.3 s
Jul 18, 20264.4 s
Jul 25, 20264.4 s
Aug 1, 20264.4 s
Aug 8, 20264.5 s
Aug 15, 20264.4 s
Aug 22, 20264.4 s
Aug 29, 20264.4 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.1 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.2 s
Oct 17, 20264.4 s
Oct 24, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
291 ms256 msMay 9Oct 24272 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026287 ms
May 16, 2026271 ms
May 23, 2026263 ms
May 30, 2026260 ms
Jun 6, 2026263 ms
Jun 13, 2026270 ms
Jun 20, 2026277 ms
Jun 27, 2026278 ms
Jul 4, 2026277 ms
Jul 11, 2026277 ms
Jul 18, 2026275 ms
Jul 25, 2026274 ms
Aug 1, 2026275 ms
Aug 8, 2026273 ms
Aug 15, 2026270 ms
Aug 22, 2026272 ms
Aug 29, 2026272 ms
Sep 5, 2026279 ms
Sep 12, 2026281 ms
Sep 19, 2026279 ms
Sep 26, 2026279 ms
Oct 3, 2026277 ms
Oct 10, 2026274 ms
Oct 17, 2026273 ms
Oct 24, 2026272 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 niazi.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. niazi.com.br at 0.6 s0.6 s
  2. niazi.com.br at 1.1 s1.1 s
  3. niazi.com.br at 1.7 s1.7 s
  4. niazi.com.br at 2.3 s2.3 s
  5. niazi.com.br at 2.9 s2.9 s
  6. niazi.com.br at 3.4 s3.4 s
  7. niazi.com.br at 4.0 s4.0 s
  8. niazi.com.br at 4.6 s4.6 s

Speed

11 to fix46
  • Reduce unused JavaScript

    6.3 s · 902 KiB

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

  • Use efficient cache lifetimes

    1.6 s · 355 KiB

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

  • Reduce unused CSS

    1.1 s · 93 KiB

    About 93 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 46

    46/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, vtexassets.com and Google CDN and others), adding 2.6 MB and 1.5 s of main-thread time.

  • Legacy JavaScript

    500 ms · 71 KiB

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

  • vtexassets.com adds 330 ms

    330 ms

    vtexassets.com costs a phone 330 ms of main-thread work and 863 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.

  • Google Tag Manager adds 344 ms

    344 ms

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

  • Google CDN adds 288 ms

    288 ms

    Google CDN costs a phone 288 ms of main-thread work and 737 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

    300 ms

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

  • Main-thread work: 3.0 s

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

  • Improve image delivery

    150 ms · 51 KiB

    3 images could be 51 KiB 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.

  • 13 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

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

    56 ms

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

Core Web Vitals

10 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 CLS: 0.74

    0.74

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

  • First Contentful Paint: 8.7 s

    8.7 s

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

  • Largest Contentful Paint: 19.7 s

    19.7 s

    Your largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A imagem divulga uma promoção de árvores de Natal com 20% d…”.

  • Time to Interactive: 19.8 s

    19.8 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • Real-user INP: 237 ms

    237 ms

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 803 ms

    803 ms

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

  • Total Blocking Time: 418 ms

    418 ms

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

2 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.3 MB in 119 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 119 requests on a phone: scripts 2.3 MB (55), other files 374 KiB (40) and HTML 204 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (63 KiB) 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.

  • About 0.9 g of CO₂ per visit

    0.93 g

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

2 checks passed
  • 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 9292
  • 2 buttons without a name

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

  • 2 text elements with low contrast

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

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

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

  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 10078
  • No H1 headline

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

  • Meta description is long (166 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization 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.

  • 18 internal links, 0 external

    The homepage links to 18 pages on niazi.com.br and 0 external pages.

4 checks passed
  • Title: 59 characters

    Your title is a healthy 59 characters: “Niazi Chohfi | 90 Anos de Qualidade e Tradição Niazi Chohfi”.

  • Canonical URL set

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

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

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    6%

    A phone browser shows 961 words, but the HTML your server sends has only 58. 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 llms.txt

    There is no https://www.niazi.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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

Other pages

4 to fix81
  • 1 linked page hidden from search

    https://www.niazi.com.br/268 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 7 pages share a meta description

    https://www.niazi.com.br/268, https://www.niazi.com.br/cortinasobmedida, https://www.niazi.com.br/artesanato-casa, https://www.niazi.com.br/cama-casa, https://www.niazi.com.br/banho-casa and https://www.niazi.com.br/mesa-casa and 1 other use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.niazi.com.br/cortinasobmedida, whose canonical is https://www.niazi.com.br/sob-medida. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 12 pages without an H1

    https://www.niazi.com.br/tecidos-casa, https://www.niazi.com.br/tapete-casa, https://www.niazi.com.br/cortinasobmedida, https://www.niazi.com.br/listalojas, https://www.niazi.com.br/christmas and https://www.niazi.com.br/decoracao-casa and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.niazi.com.br/cama, https://www.niazi.com.br/natal/arvores-de-natal, https://www.niazi.com.br/christmas, https://www.niazi.com.br/decoracao-casa, https://www.niazi.com.br/artesanato-casa and https://www.niazi.com.br/banho-casa took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 24 small tap targets

    24 of 50 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 “Cannot read properties of undefined (reading 'getRegistrations')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 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 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 961 words of copy

    The homepage carries about 961 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and TikTok Pixel.

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

  • 9 cookies set on arrival

    9

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

  • 24 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on niazi.com.br, including 21 speed issues, 4 SEO issues and 4 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