Website review, no card needed
dudeco.pt website review
Visit site (opens in a new tab)Reviewed 16 November 202630 issues · 86 checks
This review found 30 issues worth fixing on dudeco.pt, 11 of them high impact, across 86 checks. The most urgent: page weight: 31.1 MB in 387 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
86B- #11,535 of 117,426 reviewed websitesbeats 86%
- #7,095 of 66,901 online storesbeats 85%
- #6,882 of 61,008 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.5 s |
| Nov 7, 2026 | 2.4 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 199 ms |
| Jun 13, 2026 | 210 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 219 ms |
| Jul 4, 2026 | 212 ms |
| Jul 11, 2026 | 219 ms |
| Jul 18, 2026 | 227 ms |
| Jul 25, 2026 | 218 ms |
| Aug 1, 2026 | 222 ms |
| Aug 8, 2026 | 216 ms |
| Aug 15, 2026 | 255 ms |
| Aug 22, 2026 | 279 ms |
| Aug 29, 2026 | 300 ms |
| Sep 5, 2026 | 310 ms |
| Sep 12, 2026 | 276 ms |
| Sep 19, 2026 | 283 ms |
| Sep 26, 2026 | 271 ms |
| Oct 3, 2026 | 264 ms |
| Oct 10, 2026 | 272 ms |
| Oct 17, 2026 | 250 ms |
| Oct 24, 2026 | 247 ms |
| Oct 31, 2026 | 243 ms |
| Nov 7, 2026 | 226 ms |
| Nov 14, 2026 | 252 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
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.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 (Shopify, Google Tag Manager and Clarity and others), adding 1.9 MB and 879 ms of main-thread time.
Mobile performance score: 86
86/100Your mobile performance score is 86. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused JavaScript
707 KiBAbout 707 KiB of JavaScript is downloaded but never used on this page.
Shopify adds 306 ms
306 msShopify costs a phone 306 ms of main-thread work and 1.0 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.
2,234 HTML elements
The page has 2,234 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 178 ms
178 msGoogle Tag Manager costs a phone 178 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.
Minify JavaScript
150 ms · 67 KiB67 KiB could be saved by minifying JavaScript.
Improve image delivery
175 KiB7 images could be 175 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
72 KiB9 files are served with short cache lifetimes, so returning visitors download them again (72 KiB).
Reduce unused CSS
23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
16 KiB16 KiB JavaScript is shipped twice across bundles.
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: 11 ms
11 msYour server sent the HTML in 11 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.
Time to Interactive: 18.9 s
18.9 sThe page becomes fully interactive after 18.9 s. Good is under 3.8 s.
Real-user INP: 252 ms
252 msReal visitors wait 252 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 178 ms to 252 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.7 s
3.7 sYour largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NOVIDADES QUE VÃO MUDAR A SUA CASA”.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 434 ms
434 msReal visitors wait 434 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 152 ms
152 msScripts block the page for only 152 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 31.1 MB in 387 requests
31.1 MBYour homepage downloads 31.1 MB in 387 requests on a phone: media 27.2 MB (2), scripts 1.8 MB (104) and other files 1.4 MB (220). Under 2 MB keeps phones on slow connections fast.
About 8.8 g of CO₂ per visit
8.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.82 g of CO₂e: 1058.2 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
Invalid ARIA attributes
6 elements use ARIA attributes their role does not allow, which confuses screen readers.
Hidden but focusable
6 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (5 elements)
Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
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.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 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 62 images in the HTML carry an alt attribute.
57 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 57 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
210 internal links, 6 external
The homepage links to 210 pages on dudeco.pt and 6 external pages.
7 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Na Dudeco, transformamos espaços com design inovador, qualidade e atendimento excecional. Decoração funcional e acolhed…”.
Title: 35 characters
Your title is a healthy 35 characters: “Dudeco - Loja de Móveis e Decoração”.
Canonical URL set
The canonical URL is https://dudeco.pt/.
Structured data in place
Structured data found: Organization 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://dudeco.pt/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,177 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://dudeco.pt/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages slow to respond
https://dudeco.pt/collections/cadeiras-de-interior and https://dudeco.pt/collections/cadeiras-de-escritorio took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 71 found) and read each the way a search engine does.
7 checks passed
Linked pages load
8 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 8 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 8 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
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”.
2 checks passed
Tap targets are thumb-sized
113 of 140 tappable elements near the top are at least 24 px.
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 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 853 words of copy
The homepage carries about 853 words of visible text.
4 checks passed
8 short forms
8 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 108 testimonial or review blocks and 8 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
32 other companies contacted
Loading the homepage contacts 32 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 dudeco.pt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Essential A B Testing · Timesact Pre Order · Klaviyo Email Marketing Sms · Pumper Bundles · Sami Wholesale · Bundler Bundles App · Judge Me Reviews · Ez Terms And Conditions Checkbox · Apphero Free Gift · Forms · Product Labels And Badges · Blockify Checkout Rules · Appstle Loyalty · sequra.com · nice-team.net · amazonaws.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on dudeco.pt, including 14 speed issues, 1 SEO issue and 2 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.