Website review, no card needed

concordia.inf.br logo

concordia.inf.br website review

Visit site (opens in a new tab)Reviewed 25 October 202653 issues · 94 checks

This review found 53 issues worth fixing on concordia.inf.br, 21 of them high impact, across 94 checks. The most urgent: page weight: 11.2 MB in 232 requests. 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.6 s2.2 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
266 ms169 msMay 2Oct 17255 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026182 ms
May 9, 2026180 ms
May 16, 2026192 ms
May 23, 2026198 ms
May 30, 2026198 ms
Jun 6, 2026206 ms
Jun 13, 2026207 ms
Jun 20, 2026206 ms
Jun 27, 2026209 ms
Jul 4, 2026210 ms
Jul 11, 2026202 ms
Jul 18, 2026202 ms
Jul 25, 2026201 ms
Aug 1, 2026203 ms
Aug 8, 2026208 ms
Aug 15, 2026218 ms
Aug 22, 2026229 ms
Aug 29, 2026228 ms
Sep 5, 2026234 ms
Sep 12, 2026236 ms
Sep 19, 2026238 ms
Sep 26, 2026241 ms
Oct 3, 2026244 ms
Oct 10, 2026251 ms
Oct 17, 2026255 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 concordia.inf.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. concordia.inf.br at 1.1 s1.1 s
  2. concordia.inf.br at 2.2 s2.2 s
  3. concordia.inf.br at 3.3 s3.3 s
  4. concordia.inf.br at 4.4 s4.4 s
  5. concordia.inf.br at 5.5 s5.5 s
  6. concordia.inf.br at 6.6 s6.6 s
  7. concordia.inf.br at 7.7 s7.7 s
  8. concordia.inf.br at 8.8 s8.8 s

Speed

11 to fix54
  • Main-thread work: 5.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Tray Commerce and others), adding 10.9 MB and 1.3 s of main-thread time.

  • Tray Commerce adds 207 ms

    207 ms

    Tray Commerce costs a phone 207 ms of main-thread work and 9.3 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.

  • Reduce unused JavaScript

    250 ms · 785 KiB

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

  • Use efficient cache lifetimes

    600 ms · 422 KiB

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

  • Mobile performance score: 54

    54/100

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

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 688 ms

    688 ms

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

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

  • 2,963 HTML elements

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

  • Facebook adds 252 ms

    252 ms

    Facebook costs a phone 252 ms of main-thread work and 310 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.

  • Reduce unused CSS

    150 ms · 43 KiB

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

  • Improve image delivery

    44 KiB

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

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 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 JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 46 ms

    46 ms

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

Core Web Vitals

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

  • Speed Index: 16.0 s

    16.0 s

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

  • Time to Interactive: 45.1 s

    45.1 s

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

  • Total Blocking Time: 861 ms

    861 ms

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

  • Real-user INP: 219 ms

    219 ms

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

  • Real-user CLS: 0.19

    0.19

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

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

    +40%

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

  • Cumulative Layout Shift: 0.17

    0.17

    The layout shifts by 0.17 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CZ238F 200”.

  • 16 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

3 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 775 ms

    775 ms

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

Images and page weight

2 to fix55
  • Page weight: 11.2 MB in 232 requests

    11.2 MB

    Your homepage downloads 11.2 MB in 232 requests on a phone: images 9.1 MB (55), scripts 1.8 MB (68) and other files 178 KiB (97). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 8.5 MB together. On a phone connection a single image that size takes seconds.

  • 2 images below the first screen load straight away

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

  • About 3.2 g of CO₂ per visit

    3.16 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

13 to fixGoogle 6983
  • 3 buttons without a name

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

  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • Hidden but focusable

    17 elements hidden from screen readers can still receive keyboard focus.

  • Interactive controls must not be nested (9 elements)

    Interactive controls must not be nested: 9 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (6 elements)

    ARIA input fields must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.

  • 6 text elements with low contrast

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 2 images without alt text

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

  • 6 links without text

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

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

3 to fixGoogle 10086
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Saiba antes!”). One clear main headline is easier for people and search engines.

  • Meta description is long (199 characters)

    Your meta description is 199 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.

  • 255 internal links, 8 external

    The homepage links to 255 pages on concordia.inf.br and 8 external pages.

5 checks passed
  • Title: 47 characters

    Your title is a healthy 47 characters: “Conc�rdia � Inova��o e confian�a em cada clique”.

  • Canonical URL set

    The canonical URL is https://www.concordia.inf.br/.

  • 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.concordia.inf.br/sitemap.xml.

AI search readiness

2 to fix70
  • 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.

  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

2 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (1,481 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.concordia.inf.br/llms.txt (2 KiB, 18 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 2 pages without a title

    https://www.concordia.inf.br/loja/clic.php and https://www.concordia.inf.br/loja/central_anteriores.php have no <title>, so Google invents the link text in results.

  • 2 linked pages hidden from search

    https://www.concordia.inf.br/central-do-cliente and https://www.concordia.inf.br/loja/redirect_cart_service.php are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://www.concordia.inf.br/loja/clic.php, https://www.concordia.inf.br/central-do-cliente, https://www.concordia.inf.br/loja/central_anteriores.php and https://www.concordia.inf.br/loja/redirect_cart_service.php have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.concordia.inf.br/loja/clic.php, https://www.concordia.inf.br/central-do-cliente, https://www.concordia.inf.br/loja/central_anteriores.php and https://www.concordia.inf.br/loja/redirect_cart_service.php have 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 186 found) and read each the way a search engine does.

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

Best practices

3 to fixGoogle 5488
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

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

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

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

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

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

3 checks passed
  • 3 short forms

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

  • Analytics in place

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

  • Direct contact links

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

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, LinkedIn Insight 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.

  • 17 cookies set on arrival

    17

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

  • 50 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Vue.js
Analytics
Google 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 53 issues on concordia.inf.br, including 22 speed issues, 3 SEO issues 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