Website review, no card needed
ids.med.br website review
Visit site (opens in a new tab)Reviewed 30 October 202649 issues · 92 checks
This review found 49 issues worth fixing on ids.med.br, 23 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. 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
62D- #115,444 of 120,317 reviewed websitesbeats 3%
- #67,005 of 68,134 online storesbeats 1%
- #2,665 of 2,780 WooCommerce storesbeats 3%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.0 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 146 ms |
| May 16, 2026 | 147 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 144 ms |
| Jun 27, 2026 | 143 ms |
| Jul 4, 2026 | 140 ms |
| Jul 11, 2026 | 140 ms |
| Jul 18, 2026 | 142 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 143 ms |
| Aug 22, 2026 | 142 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 141 ms |
| Sep 12, 2026 | 143 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 143 ms |
| Oct 10, 2026 | 142 ms |
| Oct 17, 2026 | 144 ms |
| Oct 24, 2026 | 147 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
Speed
Use efficient cache lifetimes
16.4 s · 2.9 MB79 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).
Render-blocking requests
12.5 s46 files block the first paint until they finish downloading. Deferring or inlining them could save about 12.5 s.
Reduce unused CSS
10.5 s · 1.6 MBAbout 1.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10.5 s faster on a phone.
Reduce unused JavaScript
4.7 s · 759 KiBAbout 759 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.
Mobile performance score: 21
21/100Your mobile performance score is 21. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
900 ms · 306 KiB13 images could be 306 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, huggy.chat and rybena.com.br and others), adding 1.0 MB and 830 ms of main-thread time.
Minify CSS
450 ms · 67 KiB67 KiB could be saved by minifying CSS.
Google Tag Manager adds 426 ms
426 msGoogle Tag Manager costs a phone 426 ms of main-thread work and 355 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.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
2,025 HTML elements
The page has 2,025 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 214 ms. During a long task the page ignores taps.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Document request latency
191 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Minify JavaScript
6 KiB6 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.
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: 110 ms
110 msYour server sent the HTML in 110 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.
Real-user LCP: 6.0 s
6.0 sReal visitors wait 6.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.54
0.54For real visitors the layout shifts by 0.54 (75th percentile). Good is under 0.1.
Real-user FCP: 4.1 s
4.1 sReal visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 15.0 s
15.0 sThe first text or image appears after 15.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 32.6 s
32.6 sYour largest element takes 32.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 32.7 s
32.7 sThe page becomes fully interactive after 32.7 s. Good is under 3.8 s.
Speed Index: 15.0 s
15.0 sVisually, the page fills in at 15.0 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.465
0.465The layout shifts by 0.465 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 538 ms
538 msScripts block taps and scrolling for 538 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 146 ms to 147 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 4.8 MB in 139 requests
4.8 MBYour homepage downloads 4.8 MB in 139 requests on a phone: stylesheets 1.7 MB (42), scripts 1.7 MB (51) and images 652 KiB (24). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
unidade1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
41 KiB1 image is downloaded at several times the size a phone draws it, for example selos.png at 776 px wide, shown at 200 px. Resized copies would save about 41 KiB.
2 images in older formats
2 images (169 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.
1 image below the first screen load straight away
1 image further down the page (101 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.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.37 g of CO₂e: 164.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 buttons without a name
6 buttons have 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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
43 internal links, 6 external
The homepage links to 43 pages on ids.med.br and 6 external pages.
7 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Somos um dos maiores centros de medicina diagnóstica do interior de SP. Unidades em: Sorocaba, Piedade, Porto Feliz e A…”.
One H1 headline
Your main headline reads: “Home”.
Title: 31 characters
Your title is a healthy 31 characters: “IDS - Instituto de Diagnósticos”.
Canonical URL set
The canonical URL is https://ids.med.br/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://ids.med.br/sitemap.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://ids.med.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,856 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages point its canonical at the homepage
https://ids.med.br/2026/10/26 and https://ids.med.br/2026/10/23 declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
3 pages share a title
/, https://ids.med.br/2026/10/26 and https://ids.med.br/2026/10/23 all use the title “IDS - Instituto de Diagnósticos”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages without a meta description
https://ids.med.br/noticias-e-eventos, https://ids.med.br/unidades, https://ids.med.br/centro-de-estudos, https://ids.med.br/cartao, https://ids.med.br/exames and https://ids.med.br/resultado-dos-exames and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://ids.med.br/2026/10/26 and https://ids.med.br/2026/10/23 use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
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
32 small tap targets
32 of 69 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://api.reclameaqui.com.br/embed-raverified/hash/MTA1MTU6aWRzLWluc3RpdHV0by1kZS1kaWFnb…”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
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 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 539 words of copy
The homepage carries about 539 words of visible text.
3 checks passed
1 short form
A short form (7 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
20 other companies contacted
Loading the homepage contacts 20 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 ids.med.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
- Hosting
- OVHcloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on ids.med.br, including 24 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.