Website review, no card needed
certisign.com.br website review
Visit site (opens in a new tab)Reviewed 1 November 202645 issues · 87 checks
This review found 45 issues worth fixing on certisign.com.br, 17 of them high impact, across 87 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
61D- #114,142 of 117,972 reviewed websitesbeats 3%
- #66,238 of 67,058 online storesbeats 1%
- #2,628 of 2,706 WooCommerce storesbeats 2%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 4.8 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.9 s |
| Jul 25, 2026 | 5.2 s |
| Aug 1, 2026 | 5.5 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.3 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 202 ms |
| May 16, 2026 | 197 ms |
| May 23, 2026 | 196 ms |
| May 30, 2026 | 195 ms |
| Jun 6, 2026 | 199 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 206 ms |
| Jun 27, 2026 | 206 ms |
| Jul 4, 2026 | 210 ms |
| Jul 11, 2026 | 221 ms |
| Jul 18, 2026 | 231 ms |
| Jul 25, 2026 | 239 ms |
| Aug 1, 2026 | 246 ms |
| Aug 8, 2026 | 251 ms |
| Aug 15, 2026 | 256 ms |
| Aug 22, 2026 | 261 ms |
| Aug 29, 2026 | 266 ms |
| Sep 5, 2026 | 266 ms |
| Sep 12, 2026 | 264 ms |
| Sep 19, 2026 | 270 ms |
| Sep 26, 2026 | 270 ms |
| Oct 3, 2026 | 273 ms |
| Oct 10, 2026 | 275 ms |
| Oct 17, 2026 | 273 ms |
| Oct 24, 2026 | 270 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
How it loaded on a phone
1.4 s
2.7 s
4.1 s
5.5 s
6.9 s
8.2 s
9.6 s
11.0 s
Speed
Render-blocking requests
4.2 s44 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Use efficient cache lifetimes
1.1 s · 489 KiB9 files are served with short cache lifetimes, so returning visitors download them again (489 KiB).
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.0 s
A phone's processor spends 8.0 s on main-thread work while loading, 4.3 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, Google CDN and Facebook and others), adding 1.9 MB and 2.0 s of main-thread time.
Reduce unused JavaScript
450 ms · 837 KiBAbout 837 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 697 ms
697 msGoogle Tag Manager costs a phone 697 ms of main-thread work and 476 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.
Improve image delivery
711 KiB2 images could be 711 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 510 ms. During a long task the page ignores taps.
Google CDN adds 431 ms
431 msGoogle CDN costs a phone 431 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.
Facebook adds 304 ms
304 msFacebook costs a phone 304 ms of main-thread work and 282 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.
2,990 HTML elements
The page has 2,990 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 114 KiBAbout 114 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.
Minify JavaScript
150 ms · 25 KiB25 KiB could be saved by minifying JavaScript.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 562 ms
562 msYour server sent the HTML in 562 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 sVisually, the page fills in at 16.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 26.7 s
26.7 sThe page becomes fully interactive after 26.7 s. Good is under 3.8 s.
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “30anos-Banner-Mobile”.
First Contentful Paint: 5.8 s
5.8 sThe first text or image appears after 5.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 279 ms
279 msReal visitors wait 279 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 202 ms to 270 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 87% slower for real visitors
+87%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.032
0.032The layout barely moves while loading (CLS 0.032, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 215 requests
5.0 MBYour homepage downloads 5.0 MB in 215 requests on a phone: scripts 2.5 MB (94), images 1.5 MB (41) and HTML 474 KiB (2). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (42 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (42 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.1 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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (8 elements)
Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.
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.
38 links without text
38 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.
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Certisign | Certificado Digital, Assinatura Eletrônica e Identificação”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
167 internal links, 53 external
The homepage links to 167 pages on certisign.com.br and 53 external pages.
7 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Conheça os serviços da Certisign️: certificados digitais, TLS/SSL, assinaturas eletrônicas, soluções em biometria e ide…”.
One H1 headline
Your main headline reads: “Compre seu certificado digital”.
Canonical URL set
The canonical URL is https://certisign.com.br/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, 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://certisign.com.br/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://certisign.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,412 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
https://certisign.com.br/certificados/acessorios/token, https://certisign.com.br/certificados/acessorios/cartao and https://certisign.com.br/certificados/acessorios/leitora all use the title “:: Certisign ::”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://certisign.com.br/certificados/acessorios/token, https://certisign.com.br/certificados/acessorios/cartao and https://certisign.com.br/certificados/acessorios/leitora have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://certisign.com.br/certificados/parcerias, whose canonical is https://certisign.com.br/seja-um-parceiro. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://certisign.com.br/certificados/e-cnpj/ct-e, https://certisign.com.br/certificados/e-cnpj/nf-e and https://certisign.com.br/certificados/e-cnpj/micro-empresas-e-pme have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://certisign.com.br/certificados/acessorios/token, https://certisign.com.br/certificados/acessorios/cartao and https://certisign.com.br/certificados/acessorios/leitora 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.
3 pages slow to respond
https://certisign.com.br/certificados/e-cnpj/ct-e, https://certisign.com.br/certificados/e-cnpj/nf-e and https://certisign.com.br/certificados/e-cnpj/micro-empresas-e-pme took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 found) and read each the way a search engine does.
3 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=56282873&Ver=2&mid=6c99dd79-ab1d-42a4-8f99-f10e87a7399a&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Certisign%20%7C%20Certificado%20Digital,%20Assinatura%2.
12 small tap targets
12 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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 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 626 words of copy
The homepage carries about 626 words of visible text.
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 42 testimonial or review blocks and 7 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Matomo.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 3 mores (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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 1 of them by other companies (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.
30 other companies contacted
Loading the homepage contacts 30 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 certisign.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
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager | Matomo
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on certisign.com.br, including 25 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.