Programmable

Website review, no card needed

tecsinapse.com.br logo

tecsinapse.com.br website review

Visit site (opens in a new tab)Reviewed 21 October 202627 issues · 72 checks

This review found 27 issues worth fixing on tecsinapse.com.br, 6 of them high impact, across 72 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

Site score

82B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
4.9 s3.5 sMay 2Sep 54.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.7 s
May 9, 20264.0 s
May 16, 20264.1 s
May 23, 20264.3 s
May 30, 20264.6 s
Jun 6, 20264.4 s
Jun 13, 20264.2 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.5 s
Jul 11, 20264.5 s
Jul 18, 20264.5 s
Jul 25, 20264.2 s
Aug 1, 20264.1 s
Aug 8, 20264.3 s
Aug 15, 20264.5 s
Aug 22, 20264.6 s
Aug 29, 20264.6 s
Sep 5, 20264.8 s

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

tecsinapse.com.br (opens in a new tab)
Full-page screenshot of tecsinapse.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix74

  • Improve image delivery

    3.1 s · 984 KiB

    4 images could be 984 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

  • Use efficient cache lifetimes

    600 ms · 1.3 MB

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

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    150 ms · 49 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 61 KiB and 0 ms of main-thread time.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed

  • Main-thread work: 0.5 s

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

  • Server response: 197 ms

    197 ms

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

Core Web Vitals

5 to fix68

  • Largest Contentful Paint: 7.0 s

    7.0 s

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

  • Largest content (LCP) got 23% slower for real visitors

    +23%

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

  • Time to Interactive: 7.0 s

    7.0 s

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

  • 35 images without width and height

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

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

3 checks passed

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.04

    0.04

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix85

  • Page weight: 2.8 MB in 34 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 34 requests on a phone: images 1.6 MB (24), media 1.1 MB (1) and fonts 58 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.80 g

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

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

6 to fixGoogle 8691

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 5 text elements with low contrast

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • 10 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 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 (h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed

  • 42 automated accessibility rules passed

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

SEO

Google 100100

  • 34 internal links, 9 external

    The homepage links to 34 pages on tecsinapse.com.br and 9 external pages.

8 checks passed

  • Meta description: 120 characters

    Your meta description is 120 characters: “Tecnologia e inovação para garantir performance nas vendas e excelência nos resultados para montadoras e concessionárias”.

  • One H1 headline

    Your main headline reads: “Technology and innovation to assure sales performance and excellence in results for automotive dealerships and manufact…”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Automotive sector - TecSinapse”.

  • Canonical URL set

    The canonical URL is https://tecsinapse.com.br/en/automotive-sector/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.

  • 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://tecsinapse.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://tecsinapse.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 (687 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81

  • 2 pages share a title

    https://tecsinapse.com.br/en/automotive-sector and / all use the title “Automotive sector - TecSinapse”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://tecsinapse.com.br/en/about-us, https://tecsinapse.com.br/en/software-squad, https://tecsinapse.com.br/en/squad, /, https://tecsinapse.com.br/vagas and https://tecsinapse.com.br/codigodeconduta 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 /, whose canonical is https://tecsinapse.com.br/en/automotive-sector. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://tecsinapse.com.br/vagas, https://tecsinapse.com.br/codigodeconduta and https://tecsinapse.com.br/privacidade have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://tecsinapse.com.br/en/about-us, https://tecsinapse.com.br/en/software-squad, https://tecsinapse.com.br/en/squad and / took over 3 s to send their HTML from our server.

  • 7 internal pages checked

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

4 checks passed

  • Linked pages load

    All 7 pages we checked loaded without an error.

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087

  • 2 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69

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

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

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 405 words of visible text.

4 checks passed

  • 4 calls to action

    The homepage has 4 calls to action, for example “Talk to an expert” and “Download da apresentação”.

  • 4 short forms

    4 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix

  • 2 trackers load before any consent

    2

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

  • 4 cookies set on arrival

    4

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 tecsinapse.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 Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on tecsinapse.com.br, including 8 speed 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