beniwood.com website review

149 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

About 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.

21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.

Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 6.7 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

7 third-party services load with your homepage (Google CDN, Google Maps and Google Tag Manager and others), adding 2.5 MB and 1.5 s of main-thread time.

About 115 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

Google CDN costs a phone 764 ms of main-thread work and 1.1 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).

7 images could be 578 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google Maps costs a phone 418 ms of main-thread work and 716 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.

The page has 2,307 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

20 long tasks block the main thread while loading, the longest for 216 ms. During a long task the page ignores taps.

10 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 22.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 15.9 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 28.1 s. Good is under 3.8 s.

Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

28 images have no width and height attributes, so the layout jumps as each one loads.

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.

Your homepage downloads 7.5 MB in 193 requests on a phone: images 4.1 MB (83), scripts 2.3 MB (66) and fonts 376 KiB (9). Under 2 MB keeps phones on slow connections fast.

FOTOGRAMA-11-1-768x415.png weighs 518 KiB. On a phone connection a single image that size takes seconds.

13 images (1.7 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.

By the Sustainable Web Design model, a visit to your homepage emits about 2.11 g of CO₂e: 253.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

69 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

18 tap targets are too small or too close together to hit reliably with a finger.

1 frame has no title, so screen-reader users cannot tell what it contains.

1 link inside paragraphs relies on colour alone to stand out.

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 179 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

54 visible links have no text or label, so screen readers cannot say where they go.

Headings should not be empty: 16 elements on the page fail this check, rated minor by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h3 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 8 characters: “Beniwood”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links have no real href, so search engines can't follow them.

The homepage links to 76 pages on beniwood.com and 58 external pages.

There is no /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.

/proyecto/diumenge-paella, /proyecto/casa, /proyecto/on-fire, /proyecto/who-i-am, /proyecto/la-cruz and /proyecto/elefantes-equilibrios and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

/proyecto/visitante, /proyecto/diumenge-paella, /proyecto/casa, /proyecto/on-fire, /proyecto/who-i-am and /proyecto/la-cruz and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

/proyecto/casa, /proyecto/on-fire, /proyecto/who-i-am, /proyecto/la-cruz, /proyecto/elefantes-equilibrios and /proyecto/leo-creciente and 3 others 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.

/proyecto/on-fire, /proyecto/who-i-am, /proyecto/la-cruz, /proyecto/elefantes-equilibrios, /proyecto/leo-creciente and /proyecto/alexis and 4 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.

2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://beniwood.com/' was loaded over HTTPS, but requested an insecure script 'http://beni…”.

6 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Mixed content”).

1 resource load over plain http on your https page (for example http://beniwood.com/wp-content/plugins/woocommerce/assets/js/select2/select2.full.min.js?ver=4.0.3); browsers block or warn about them.

10 links from your homepage to your own site are broken, for example https://beniwood.com/proyecto/les-7-llums/ (508).

1 link to other sites is dead, for example http://linkedin.com/in/albertoevangelio (999).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

beniwood.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

beniwood.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 18 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,482 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

beniwood.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=spf.dominioabsoluto.net”.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 2 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.