Website review, no card needed
adexperu.org.pe website review
Visit site (opens in a new tab)Reviewed 18 October 202654 issues · 87 checks
This review found 54 issues worth fixing on adexperu.org.pe, 22 of them high impact, across 87 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 26, 2026 | 2.9 s |
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.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.3 s
8.5 s
9.7 s
Speed
Use efficient cache lifetimes
20.4 s · 9.7 MB68 files are served with short cache lifetimes, so returning visitors download them again (9.7 MB).
Improve image delivery
17.1 s · 5.1 MB21 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.1 s faster on a phone.
Render-blocking requests
5.0 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
Reduce unused JavaScript
3.5 s · 573 KiBAbout 573 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Reduce unused CSS
1.5 s · 270 KiBAbout 270 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 9). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Document request latency
850 ms · 1.4 MBThe HTML itself could arrive about 850 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Minify JavaScript
420 ms · 1.1 MB1.1 MB could be saved by minifying JavaScript.
Reduce initial server response time
872 msReduce initial server response time. Google estimates savings of 872 ms on a phone.
Duplicated JavaScript
350 ms · 51 KiB51 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.
Minify CSS
310 ms · 58 KiB58 KiB could be saved by minifying CSS.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 396 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 122 ms
122 msGoogle CDN costs a phone 122 ms of main-thread work and 347 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.
Server response: 972 ms
972 msYour server takes 972 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Google CDN and others), adding 976 KiB and 460 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 144 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.
Core Web Vitals
First Contentful Paint: 15.7 s
15.7 sThe first text or image appears after 15.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 47.4 s
47.4 sYour largest element takes 47.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “En ADEX ofrecemos una completa gama de servicios empresaria…”.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 48.1 s
48.1 sThe page becomes fully interactive after 48.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.257
0.257The layout shifts by 0.257 while loading, so content jumps under the reader's thumb. Good is under 0.1.
39 images without width and height
39 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 268 ms
268 msScripts block taps and scrolling for 268 ms in total while the page loads. Good is under 200 ms.
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
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.7 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 12.8 MB in 97 requests
12.8 MBYour homepage downloads 12.8 MB in 97 requests on a phone: images 9.1 MB (50), HTML 2.2 MB (1) and scripts 972 KiB (19). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
3.0 MB2 images are downloaded at several times the size a phone draws them, for example carousel1_18115_09-09-2026_16-50-07.jpg at 3,000 px wide, shown at 390 px. Resized copies would save about 3.0 MB.
15 images in older formats
15 images (6.2 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.
10 images below the first screen load straight away
10 images further down the page (784 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.6 g of CO₂ per visit
3.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.63 g of CO₂e: 435.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
15 buttons without a name
15 buttons have no accessible name, so screen readers announce just “button”.
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
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.
35 images without alt text
35 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (31 elements)
All page content should be contained by landmarks: 31 elements on the page fail 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.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h5, h1 → h5 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (13 characters)
Your title is only 13 characters: “ADEX - Inicio”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
5 H1 headlines
There are 5 <h1> headlines (“Nuestros Servicios”, “Conoce nuestros sectores” and “ADEX hoy”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
No XML sitemap
No XML sitemap at https://adexperu.org.pe/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at adexperu.org.pe/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
26 internal links, 36 external
The homepage links to 26 pages on adexperu.org.pe and 36 external pages.
AI search readiness
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://adexperu.org.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (504 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages without a meta description
https://adexperu.org.pe/adex/asociate, https://adexperu.org.pe/adex/nosotros, https://adexperu.org.pe/adex/servicios, https://adexperu.org.pe/adex/educacion, https://adexperu.org.pe/adex/adexhoy and https://adexperu.org.pe/adex/eventos and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages with very little text
https://adexperu.org.pe/adex/servicios, https://adexperu.org.pe/adex/adexhoy and https://adexperu.org.pe/adex/eventos 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.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 7 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.
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 7 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 9 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 “Cannot read properties of undefined (reading 'filter')”.
3 distorted images
3 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.
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 560 words of copy
The homepage carries about 560 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
10 other companies contacted
Loading the homepage contacts 10 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 adexperu.org.pe, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on adexperu.org.pe, including 21 speed issues, 9 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.