Website review, no card needed
segurex.com website review
Visit site (opens in a new tab)Reviewed 24 October 202630 issues · 77 checks
This review found 30 issues worth fixing on segurex.com, 14 of them high impact, across 77 checks. The most urgent: render-blocking 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
80B- #43,542 of 109,987 reviewed websitesbeats 55%
- #28,972 of 62,419 online storesbeats 47%
- #581 of 2,534 WooCommerce storesbeats 73%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.7 s |
| May 9, 2026 | 4.9 s |
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.9 s |
| May 30, 2026 | 4.9 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 5.3 s |
| Jun 20, 2026 | 5.3 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 4.6 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 204 ms |
| May 9, 2026 | 203 ms |
| May 16, 2026 | 197 ms |
| May 23, 2026 | 209 ms |
| May 30, 2026 | 207 ms |
| Jun 6, 2026 | 208 ms |
| Jun 13, 2026 | 213 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 197 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 184 ms |
| Aug 1, 2026 | 184 ms |
| Aug 8, 2026 | 189 ms |
| Aug 15, 2026 | 192 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 194 ms |
| Sep 26, 2026 | 199 ms |
| Oct 3, 2026 | 201 ms |
| Oct 10, 2026 | 194 ms |
| Oct 17, 2026 | 206 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
Render-blocking requests
5.0 s101 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 · 665 KiBAbout 665 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.
Use efficient cache lifetimes
1.6 s · 330 KiB119 files are served with short cache lifetimes, so returning visitors download them again (330 KiB).
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 76). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.4 MB and 707 ms of main-thread time.
Google Tag Manager adds 455 ms
455 msGoogle Tag Manager costs a phone 455 ms of main-thread work and 846 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,937 HTML elements
The page has 1,937 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need.
Reduce unused CSS
29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
20 KiB20 KiB could be saved by minifying JavaScript.
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: 44 ms
44 msYour server sent the HTML in 44 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 FCP: 4.2 s
4.2 sReal visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 16.9 s
16.9 sYour largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “slider-addi-3”.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Time to Interactive: 17.0 s
17.0 sThe page becomes fully interactive after 17.0 s. Good is under 3.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 204 ms to 206 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.7 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Total Blocking Time: 80 ms
80 msScripts block the page for only 80 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.4 MB in 164 requests
2.4 MBYour homepage downloads 2.4 MB in 164 requests on a phone: scripts 1.8 MB (81), images 416 KiB (14) and stylesheets 150 KiB (53). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 83.1 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
4 text elements with low contrast
4 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 (11 elements)
All page content should be contained by landmarks: 11 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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 50 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 3 mores 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.
184 internal links, 13 external
The homepage links to 184 pages on segurex.com and 13 external pages.
7 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Compra cerraduras mecánicas, digitales e inteligentes y soluciones de acceso para hogares, negocios y proyectos. Servic…”.
Title: 42 characters
Your title is a healthy 42 characters: “Segurex - Soluciones de acceso y seguridad”.
Canonical URL set
The canonical URL is https://segurex.com/.
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.
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://segurex.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://segurex.com/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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (875 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://segurex.com/tipo-de-cerraduras-principal/cerraduras-mecanicas, https://segurex.com/tipo-de-cerraduras-principal/cerraduras-para-bano, https://segurex.com/tipo-de-cerraduras-principal/cerraduras-para-alcoba, https://segurex.com/tipos-de-cerradura/cerraduras-para-entrada-principal, https://segurex.com/tipos-de-cerradura/cerrojos-de-seguridad and https://segurex.com/tipos-de-cerradura/cerraduras-de-sobreponer and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages slow to respond
https://segurex.com/tipos-de-cerradura/cerraduras-digitales, https://segurex.com/tipos-de-cerradura/cerraduras-inteligentes-para-airbnb, https://segurex.com/tipo-de-cerraduras-principal/cerraduras-mecanicas, https://segurex.com/tipo-de-cerraduras-principal/cerraduras-para-bano, https://segurex.com/tipo-de-cerraduras-principal/cerraduras-para-alcoba and https://segurex.com/tipos-de-cerradura/cerraduras-para-entrada-principal and 7 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 60 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.
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 15 pages that loaded have a <title>.
Best practices
40 small tap targets
40 of 126 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.doofinder.com/livelayer/1.8.209/css/2/common.css?v=1.8.209' from origin 'https…”.
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 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 664 words of copy
The homepage carries about 664 words of visible text.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
23 other companies contacted
Loading the homepage contacts 23 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 segurex.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- Vue.js
- E-commerce
- WooCommerce
- Analytics
- Google 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 30 issues on segurex.com, including 15 speed issues, 1 SEO issue 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.