Website review, no card needed

larconstrutora.com.br logo

larconstrutora.com.br website review

Visit site (opens in a new tab)Reviewed 2 November 202634 issues · 76 checks

This review found 34 issues worth fixing on larconstrutora.com.br, 9 of them high impact, across 76 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
2.3 s860 msMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.5 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.1 s
Jul 25, 20261.0 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Oct 10, 20261.5 s
Oct 17, 20261.6 s
Oct 24, 20261.4 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
179 ms55 msMay 16Oct 1797 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202686 ms
May 23, 202682 ms
May 30, 202679 ms
Aug 1, 202670 ms
Aug 8, 202669 ms
Aug 15, 202678 ms
Aug 22, 202683 ms
Aug 29, 202679 ms
Sep 5, 202685 ms
Sep 12, 2026105 ms
Sep 19, 2026124 ms
Sep 26, 2026114 ms
Oct 3, 2026165 ms
Oct 17, 202697 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 larconstrutora.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix70
  • Reduce unused JavaScript

    1.1 s · 180 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Improve image delivery

    750 ms · 1.2 MB

    22 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • 6 third-party services on the page

    6 third-party services load with your homepage (website-files.com, cloudfront.net and Google CDN and others), adding 8.4 MB and 154 ms of main-thread time.

  • Mobile performance score: 70

    70/100

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

  • website-files.com adds 85 ms

    85 ms

    website-files.com costs a phone 85 ms of main-thread work and 8.2 MB 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.

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    20 KiB

    About 20 KiB of CSS is downloaded but never applied on this page.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 9.5 s

    9.5 s

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

  • Time to Interactive: 9.6 s

    9.6 s

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

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

    +56%

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

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

  • 20 images without width and height

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

8 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: 1.3 s

    1.3 s

    Real visitors wait 1.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.0 s

    1.0 s

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

  • Real-user TTFB: 506 ms

    506 ms

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

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

    -27%

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

  • Total Blocking Time: 118 ms

    118 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

4 to fix43
  • Page weight: 8.7 MB in 57 requests

    8.7 MB

    Your homepage downloads 8.7 MB in 57 requests on a phone: images 8.2 MB (34), scripts 459 KiB (12) and fonts 104 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (517 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.

  • 5 images below the first screen load straight away

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

  • 1 image far larger than shown

    25 KiB

    1 image is downloaded at several times the size a phone draws it, for example 65412a7b40108e4e6159e938_00-Restaurantes-LOGO-Starbucks-p-50 at 390 px wide, shown at 96 px. Resized copies would save about 25 KiB.

  • About 2.5 g of CO₂ per visit

    2.48 g

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

Accessibility

4 to fixGoogle 9595
  • All page content should be contained by landmarks (14 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 28 links without text

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

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

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

2 checks passed
  • Every image has alt text

    All 28 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

5 to fixGoogle 9274
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“Construtora que pensa como o cliente.”, “CLIENTES” and “DEPOIMENTOS”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • No X (Twitter) card tag

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

  • 64 internal links, 6 external

    The homepage links to 64 pages on larconstrutora.com.br and 6 external pages.

3 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “LAR Construtora | A Construtora que Pensa como Cliente”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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.larconstrutora.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.

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

Other pages

2 to fix90
  • 6 pages without a meta description

    https://www.larconstrutora.com.br/sobre, https://www.larconstrutora.com.br/novidades, https://www.larconstrutora.com.br/contato, https://www.larconstrutora.com.br/lar-id, https://www.larconstrutora.com.br/lar-id-venda and https://www.larconstrutora.com.br/segmento/edificacoes have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.larconstrutora.com.br/clientes, https://www.larconstrutora.com.br/contato, https://www.larconstrutora.com.br/lar-id, https://www.larconstrutora.com.br/lar-id-venda and https://www.larconstrutora.com.br/segmento/edificacoes have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://www.larconstrutora.com.br/contato, https://www.larconstrutora.com.br/clients/pedrart, https://www.larconstrutora.com.br/clients/arturito, https://www.larconstrutora.com.br/clients/shoulder, https://www.larconstrutora.com.br/clients/tramontina-store and https://www.larconstrutora.com.br/clients/tok-stok and 3 others have 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

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

Best practices

1 to fixGoogle 7393
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.larconstrutora.com.br/' was loaded over HTTPS, but requested an insecure styles…”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

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

  • Only about 142 words

    The homepage has only about 142 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 3 cookies set on arrival

    3

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 larconstrutora.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
Webflow
Framework
jQuery
Analytics
Google Analytics
Hosting
Webflow

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on larconstrutora.com.br, including 12 speed issues, 5 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