Website review, no card needed
facephi.com website review
Visit site (opens in a new tab)Reviewed 30 October 202626 issues · 77 checks
This review found 26 issues worth fixing on facephi.com, 8 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.9 s |
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.2 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.5 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.7 s |
| Oct 24, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 747 ms |
| May 16, 2026 | 738 ms |
| May 23, 2026 | 767 ms |
| May 30, 2026 | 942 ms |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 954 ms |
| Jun 20, 2026 | 898 ms |
| Jun 27, 2026 | 812 ms |
| Jul 4, 2026 | 805 ms |
| Jul 11, 2026 | 889 ms |
| Jul 18, 2026 | 947 ms |
| Jul 25, 2026 | 928 ms |
| Aug 1, 2026 | 891 ms |
| Aug 8, 2026 | 918 ms |
| Aug 15, 2026 | 893 ms |
| Aug 22, 2026 | 897 ms |
| Aug 29, 2026 | 917 ms |
| Sep 5, 2026 | 946 ms |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.0 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
Speed
3,055 HTML elements
The page has 3,055 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
900 ms · 150 KiBAbout 150 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 998 ms. During a long task the page ignores taps.
Render-blocking requests
950 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused CSS
600 ms · 113 KiBAbout 113 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (JSDelivr CDN, cookiebot.eu and Cloudflare and others), adding 414 KiB and 144 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
5 KiB2 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).
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: 7 ms
7 msYour server sent the HTML in 7 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 INP: 647 ms
647 msReal visitors wait 647 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 8.5 s
8.5 sYour largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Identidad Continua Cada señal Todo el contexto Sigue la señ…”.
Time to Interactive: 10.0 s
10.0 sThe page becomes fully interactive after 10.0 s. Good is under 3.8 s.
Total Blocking Time: 827 ms
827 msScripts block taps and scrolling for 827 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 51% slower for real visitors
+51%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 747 ms to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.9 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.41 g of CO₂e: 49.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.4 MB in 59 requests
1.4 MBYour homepage downloads 1.4 MB in 59 requests on a phone: scripts 805 KiB (30), images 262 KiB (9) and fonts 193 KiB (4). That is a lean page.
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
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 13 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Facephi: Expertos en verificación biométrica de la identidad digital”.
146 internal links, 4 external
The homepage links to 146 pages on facephi.com and 4 external pages.
7 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Especialistas en la protección y verificación de la identidad mediante soluciones tecnológicas que crean procesos libre…”.
One H1 headline
Your main headline reads: “Identidad Continua”.
Canonical URL set
The canonical URL is https://facephi.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://facephi.com/sitemap_index.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,377 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://facephi.com/llms.txt (13 KiB, 10 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://facephi.com/changelog has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 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
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
21 of 25 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
A 24-field form
Your longest form asks for 24 fields (11 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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,488 words of copy
The homepage carries about 1,488 words of visible text.
3 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
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.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 facephi.com, 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
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on facephi.com, including 18 speed issues, 1 SEO issue and 5 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.