Website review, no card needed

smartlead.com.br logo

smartlead.com.br website review

Visit site (opens in a new tab)Reviewed 9 November 202635 issues · 76 checks

This review found 35 issues worth fixing on smartlead.com.br, 15 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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 smartlead.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix50
  • Use efficient cache lifetimes

    6.8 s · 2.6 MB

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

  • Improve image delivery

    1.8 s · 1.1 MB

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

  • Render-blocking requests

    1.2 s

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Main-thread work: 4.4 s

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

  • Reduce unused JavaScript

    750 ms · 606 KiB

    About 606 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Hotjar and others), adding 1.3 MB and 1.1 s of main-thread time.

  • Mobile performance score: 50

    50/100

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

  • Google CDN adds 420 ms

    420 ms

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

  • Font display

    300 ms

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

  • 1,597 HTML elements

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

  • 17 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 48 KiB

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

  • Legacy JavaScript

    150 ms · 37 KiB

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

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 18 ms

    18 ms

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

Core Web Vitals

5 to fix48
  • Largest Contentful Paint: 12.2 s

    12.2 s

    Your largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sua empresa cresceu, mas seu sistema ainda gera planilhas, …”.

  • Time to Interactive: 20.1 s

    20.1 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • Total Blocking Time: 685 ms

    685 ms

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

  • 20 images without width and height

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

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

2 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

4 to fix38
  • Page weight: 5.2 MB in 93 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 93 requests on a phone: images 3.1 MB (33), scripts 1.4 MB (31) and other files 359 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Group-64325-2.png weighs 822 KiB. On a phone connection a single image that size takes seconds.

  • 5 images in older formats

    5 images (2.0 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.

  • 3 images below the first screen load straight away

    3 images further down the page (973 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.48 g

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

6 to fixGoogle 8291
  • 7 text elements with low contrast

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Zoom is disabled

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

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

1 to fixGoogle 9297
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 28 internal links, 0 external

    The homepage links to 28 pages on smartlead.com.br and 0 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Somos uma empresa de desenvolvimento de softwares e aplicativos customizados, nossos desenvolvedores de software estão …”.

  • One H1 headline

    Your main headline reads: “Nós somos os desenvolvedores de softwares e aplicativos que você estava buscando.”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Smartlead - Desenvolvimento de softwares e aplicativos”.

  • Canonical URL set

    The canonical URL is https://smartlead.com.br/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://smartlead.com.br/sitemap_index.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://smartlead.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 (1,425 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 12 pages without a meta description

    https://smartlead.com.br/contato, https://smartlead.com.br/cases, https://smartlead.com.br/sobre, https://smartlead.com.br/metodologia, https://smartlead.com.br/home-2 and https://smartlead.com.br/servico/aplicativos and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

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

  • 1 page with very little text

    https://smartlead.com.br/cases has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 14 internal pages checked

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

5 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

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

Best practices

2 to fixGoogle 9291
  • 4 small tap targets

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

  • Thin social proof

    Social proof on the homepage: 13 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

2 checks passed
  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, Hotjar and Cloudflare Web Analytics.

  • Direct contact links

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

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, Hotjar and 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.

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

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

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Hotjar
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on smartlead.com.br, including 15 speed issues, 1 SEO issue 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