Website review, no card needed
mali.pe website review
Visit site (opens in a new tab)Reviewed 29 October 202648 issues · 91 checks
This review found 48 issues worth fixing on mali.pe, 27 of them high impact, across 91 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
53F- #120,298 of 120,865 reviewed websitesbeats 0%
- #68,377 of 68,427 online storesbeats 0%
- #2,797 of 2,800 WooCommerce storesbeats 0%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Sep 19, 2026 | 5.1 s |
| Sep 26, 2026 | 5.0 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 5.1 s |
| Oct 17, 2026 | 5.0 s |
| Oct 24, 2026 | 5.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 19, 2026 | 124 ms |
| Sep 26, 2026 | 124 ms |
| Oct 3, 2026 | 123 ms |
| Oct 10, 2026 | 126 ms |
| Oct 17, 2026 | 124 ms |
| Oct 24, 2026 | 126 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
33.8 s · 9.2 MB215 files are served with short cache lifetimes, so returning visitors download them again (9.2 MB).
Render-blocking requests
23.6 s132 files block the first paint until they finish downloading. Deferring or inlining them could save about 23.6 s.
Reduce unused JavaScript
16.6 s · 3.2 MBAbout 3.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 16.6 s faster on a phone.
Improve image delivery
1.9 s · 2.2 MB19 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Reduce unused CSS
1.1 s · 241 KiBAbout 241 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 4
4/100Your mobile performance score is 4. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 816 ms. During a long task the page ignores taps.
Minify JavaScript
300 ms · 48 KiB48 KiB could be saved by minifying JavaScript.
Google Maps adds 169 ms
169 msGoogle Maps costs a phone 169 ms of main-thread work and 396 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.
1,510 HTML elements
The page has 1,510 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
FontAwesome CDN adds 0 ms
0 msFontAwesome CDN costs a phone 0 ms of main-thread work and 304 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.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Google Maps and FontAwesome CDN and others), adding 893 KiB and 348 ms of main-thread time.
Legacy JavaScript
200 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify CSS
150 ms · 10 KiB10 KiB could be saved by minifying CSS.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
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: 93 ms
93 msYour server sent the HTML in 93 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: 7.0 s
7.0 sReal visitors wait 7.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.73
0.73For real visitors the layout shifts by 0.73 (75th percentile). Good is under 0.1.
Real-user FCP: 5.8 s
5.8 sReal visitors see the first content after 5.8 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 22.9 s
22.9 sThe first text or image appears after 22.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 37.5 s
37.5 sYour largest element takes 37.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Pacchas: agua, ritual y ofrenda en los Andes”.
Speed Index: 22.9 s
22.9 sVisually, the page fills in at 22.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 37.5 s
37.5 sThe page becomes fully interactive after 37.5 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.775
0.775The layout shifts by 0.775 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
4 images without width and height
4 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 124 ms to 126 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 5.1 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 127 ms
127 msReal visitors wait 127 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 9.8 MB in 231 requests
9.8 MBYour homepage downloads 9.8 MB in 231 requests on a phone: scripts 5.2 MB (133), images 3.9 MB (31) and stylesheets 366 KiB (52). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.
23 images in older formats
23 images (3.6 MB) 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.
An image on the first screen is lazy-loaded
Slide-Web-600x218.jpg 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).
9 images far larger than shown
133 KiB9 images are downloaded at several times the size a phone draws them, for example Captura-de-pantalla-2026-07-17-092111-2-1024x427.png at 1,024 px wide, shown at 330 px. Resized copies would save about 133 KiB.
2 images below the first screen load straight away
2 images further down the page (54 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.8 g of CO₂ per visit
2.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.79 g of CO₂e: 334.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 79 images in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No robots.txt
There is no robots.txt at mali.pe/robots.txt, the first file search crawlers ask for.
93 internal links, 13 external
The homepage links to 93 pages on mali.pe and 13 external pages.
6 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Descubre el MALI, el Museo de Arte de Lima. Explora exposiciones, actividades culturales, colecciones y experiencias de…”.
Title: 59 characters
Your title is a healthy 59 characters: “MALI | Museo de Arte de Lima – Arte, Exposiciones y Cultura”.
Canonical URL set
The canonical URL is https://mali.pe/es/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://mali.pe/sitemap.xml.
AI search readiness
No llms.txt
There is no https://mali.pe/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.
3 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading 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,538 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://mali.pe/en, which answers with an error. Visitors hit a dead end and search engines drop it.
12 pages without a meta description
https://mali.pe/es/servicios, https://mali.pe/es/entradas, https://mali.pe/es/museo/nosotros/palacio-de-la-exposicion, https://mali.pe/es/museo/vision, https://mali.pe/es/exhibition and https://mali.pe/es/activity and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://mali.pe/educacion has 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 88 found) and read each the way a search engine does.
4 checks passed
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 14 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 301 words of copy
The homepage carries about 301 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
1 checks passed
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
7 other companies contacted
Loading the homepage contacts 7 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 mali.pe, 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
- React
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
- Hosting
- AWS
Company
- Founded
- 1959
- Headquarters
- Lima
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on mali.pe, 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.