Website review, no card needed

cel.eng.br logo

cel.eng.br website review

Visit site (opens in a new tab)Reviewed 26 October 202632 issues · 75 checks

This review found 32 issues worth fixing on cel.eng.br, 14 of them high impact, across 75 checks. The most urgent: render-blocking 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

Full-page screenshot of cel.eng.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cel.eng.br at 1.2 s1.2 s
  2. cel.eng.br at 2.5 s2.5 s
  3. cel.eng.br at 3.7 s3.7 s
  4. cel.eng.br at 4.9 s4.9 s
  5. cel.eng.br at 6.2 s6.2 s
  6. cel.eng.br at 7.4 s7.4 s
  7. cel.eng.br at 8.6 s8.6 s
  8. cel.eng.br at 9.9 s9.9 s

Speed

6 to fix33
  • Render-blocking requests

    6.2 s

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

  • Font display

    2.5 s

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

  • Reduce unused JavaScript

    1.2 s · 209 KiB

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

  • Mobile performance score: 33

    33/100

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

  • Improve image delivery

    450 ms · 436 KiB

    7 images could be 436 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    610 ms · 113 KiB

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

  • Minify CSS

    160 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify JavaScript

    8 KiB

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

  • 1 third-party service on the page

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 199 ms

    199 ms

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

Core Web Vitals

6 to fix34
  • Largest Contentful Paint: 13.4 s

    13.4 s

    Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Um novo caminho Oferecendo energia para a vida”.

  • Speed Index: 15.6 s

    15.6 s

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

  • Cumulative Layout Shift: 1.044

    1.044

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

  • Time to Interactive: 13.7 s

    13.7 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • 1 image without width and height

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

1 checks passed
  • 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

2 to fix75
  • Page weight: 2.8 MB in 131 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 131 requests on a phone: images 1.9 MB (13), scripts 536 KiB (69) and stylesheets 209 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (885 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.

  • 2 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.79 g

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

5 to fixGoogle 8293
  • 3 tap targets too small

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

  • All page content should be contained by landmarks (2 elements)

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

  • Zoom is disabled

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

  • 7 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

5 to fixGoogle 7772
  • No meta description

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

  • No H1 headline

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

  • No structured data

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

  • No social preview image

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

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 37 internal links, 0 external

    The homepage links to 37 pages on cel.eng.br and 0 external pages.

4 checks passed
  • Title: 38 characters

    Your title is a healthy 38 characters: “Cel Engenharia – Crescendo com Energia”.

  • Canonical URL set

    The canonical URL is https://www.cel.eng.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.cel.eng.br/wp-sitemap.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://www.cel.eng.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 (425 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 10 pages without a meta description

    https://www.cel.eng.br/contato, https://www.cel.eng.br/en/cel-page-ingles, https://www.cel.eng.br/portfolio-item/instalacoes, https://www.cel.eng.br/portfolio-item/subestacoes, https://www.cel.eng.br/portfolio-item/cos-centro-de-operacao-de-sistema-eletrico and https://www.cel.eng.br/portfolio-item/servicos-concessionaria and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.cel.eng.br/en/cel-page-ingles has no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.cel.eng.br/contato, https://www.cel.eng.br/en/cel-page-ingles, https://www.cel.eng.br/portfolio-item/instalacoes, https://www.cel.eng.br/portfolio-item/subestacoes, https://www.cel.eng.br/portfolio-item/cos-centro-de-operacao-de-sistema-eletrico and https://www.cel.eng.br/portfolio-item/servicos-concessionaria took over 3 s to send their HTML from our server.

  • 10 internal pages checked

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

5 checks passed
  • Linked pages load

    All 10 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 10 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 395 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 cel.eng.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on cel.eng.br, including 12 speed issues, 5 SEO issues and 5 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