Website review, no card needed
arbitrade.es website review
Visit site (opens in a new tab)Reviewed 21 October 202641 issues · 87 checks
This review found 41 issues worth fixing on arbitrade.es, 19 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.8 s |
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 129 ms |
| May 9, 2026 | 129 ms |
| May 16, 2026 | 128 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 123 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 123 ms |
| Aug 29, 2026 | 118 ms |
| Sep 5, 2026 | 115 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 111 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
Reduce unused JavaScript
4.5 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Reduce unused CSS
2.7 s · 511 KiBAbout 511 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 77). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google CDN and Google Tag Manager and others), adding 2.1 MB and 738 ms of main-thread time.
Font display
900 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).
Render-blocking requests
800 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Improve image delivery
511 KiB4 images could be 511 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
YouTube adds 313 ms
313 msYouTube costs a phone 313 ms of main-thread work and 963 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.
Google CDN adds 269 ms
269 msGoogle CDN costs a phone 269 ms of main-thread work and 733 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
300 ms · 30 KiB30 KiB could be saved by minifying JavaScript.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,938 HTML elements
The page has 1,938 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 29 KiB29 KiB could be saved by minifying CSS.
Document request latency
172 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 77 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 456 ms
456 msYour server sent the HTML in 456 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: 4.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 21.5 s
21.5 sYour largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Servicio global deFood&Drink desatendido En Arbitrade, ofre…”.
Time to Interactive: 43.3 s
43.3 sThe page becomes fully interactive after 43.3 s. Good is under 3.8 s.
Cumulative Layout Shift: 1.019
1.019The layout shifts by 1.019 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
29 images without width and height
29 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 129 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 138 ms
138 msScripts block the page for only 138 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 18.2 MB in 158 requests
18.2 MBYour homepage downloads 18.2 MB in 158 requests on a phone: images 13.3 MB (91), scripts 2.2 MB (28) and fonts 1.5 MB (7). Under 2 MB keeps phones on slow connections fast.
12 images below the first screen load straight away
12 images further down the page (2.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (93 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.
About 5.1 g of CO₂ per visit
5.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.15 g of CO₂e: 617.9 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
Unlabelled dropdowns
2 dropdowns have no label.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 72 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
175 internal links, 19 external
The homepage links to 175 pages on arbitrade.es and 19 external pages.
8 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Arbitrade más de 30 años ofreciendo servicio de máquinas expendedoras a empresas con la pasión y tecnología - Llámanos:…”.
One H1 headline
Your main headline reads: “Arbitrade”.
Title: 50 characters
Your title is a healthy 50 characters: “Arbitrade | Máquinas expendedoras Servicio Vending”.
Canonical URL set
The canonical URL is https://arbitrade.es/.
Structured data in place
Structured data found: 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://arbitrade.es/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing url, 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://arbitrade.es/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 (3,503 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://arbitrade.es/aviso-legal is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
Thin social proof
Social proof on the homepage: 59 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 10-field form
Your longest form asks for 10 fields (7 required). Every extra field lowers completion.
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 1,305 words of copy
The homepage carries about 1,305 words of visible text.
2 checks passed
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie, 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.
11 other companies contacted
Loading the homepage contacts 11 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 arbitrade.es, 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
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on arbitrade.es, including 23 speed issues and 4 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.