Review
Your Website Score is
Update
Similar Ranking
27
MODO DE MANUTENÇÃO
portaldepublicidade.pt
27
ALOE VERA SHOP | LOJA ONLINE
aloe-vera.me
27
HOTEL CARVALHO ARAUJO - HOTEL CARVALHO ARAUJO HOTEL CARVALHO ARAUJO - O SEU HOTEL NO GERÊS
hotelcarvalhoaraujo.com
27
REDUCE YOUR FOOTPRINT WHILE TRAVELING THE WORLD - NO FOOTPRINT NOMADS
nofootprintnomads.com
27
CONSULTOR DE MARKETING DIGITAL? MARCO GOUVEIA
marcogouveia.pt
27
CRIAR LOJA ONLINE. VENDA EM TODO LADO COM A WEASY | WEASY.IO
weasy.io
27
RELÓGIOS, JOIAS E ÓCULOS. LUXO AOS MELHORES PREÇOS NA ZAGARI
zagari.pt
Latest Sites
12
BRIGHTON EAGLE CHAUFFEUR & TAXI - CHAUFFEUR DRIVEN EXECUTIVE CAR HIRE
brightoneaglechauffeur.com
56
U.PORTO - UNIVERSIDADE DO PORTO
sigarra.up.pt
19
DIRECT ENGLISH | O PROGRAMA DE INGLÊS MAIS EFICAZ DO MUNDO
directenglish.pt
24
THE REIGATE MARBLE SHOP | GRANITE WORKTOPS & MARBLE WORKTOPS IN SURREY AND ALL AROUND SUS---
marble-shop.co.uk
19
BLIMEY SOLUTIONS LTD - CIS ACCOUNTING & RECRUITMENT SERVICES IN LONDON
blimeysolutions.com
19
TROPOJA CONSTRUCTION LTD | TRUSTED CONSTRUCTION COMPANY IN LONDON
tropojaconstructionltd.co.uk
31
ELSONY WASTE REMOVAL | AFFORDABLE WASTE & RUBBISH COLLECTION & REMOVAL IN N11, N12 & SURROUNDING AREAS
elsonywaste.co.uk
Top Technologies
PHP
Programming Languages
Google Font API
Font Scripts
WordPress
CMS
Apache
Web Servers
Font Awesome
Font Scripts
Nginx
Web Servers
jQuery
JavaScript Frameworks
Yoast SEO
SEO
WooCommerce
Ecommerce
Google Tag Manager
Tag Managers
27
faccia.pt
Last Updated: 4 weeks
Success
62% of passed verification steps
Warning
15% of total warning
Errors
23% of total errors, require fast action
Share
Download PDF
Desktop
Mobile
Performance
Desktop Score 51%
Best Practices
Desktop Score 50%
SEO
Desktop Score 83%
PWA
Desktop Score 22%
Performance
Mobile Score 5%
Best Practices
Mobile Score 50%
SEO
Mobile Score 84%
PWA
Mobile Score 30%
Only Registered Users
Sign up for see all features and reviews about this site
Login
Only Registered Users
Sign up for see all features and reviews about this site
Login
Social Data
Only Registered Users
Sign up for see all features and reviews about this site
Login
Estimation Traffic and Earnings
Only Registered Users
Sign up for see all features and reviews about this site
Login
Desktop
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Avoid enormous network payloads
Total size was 4,159 KiB
Large network payloads cost users real money and are highly correlated with long load times
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Minify JavaScript
Potential savings of 19 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint
1.4 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint
1.3 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests
57 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Minimize third-party usage
Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Minimizes main-thread work
1.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Efficiently encode images
Potential savings of 219 KiB
Optimized images load faster and consume less cellular data
Enable text compression
Potential savings of 355 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Largest Contentful Paint
4.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Reduce unused JavaScript
Potential savings of 805 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Max Potential First Input Delay
50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve static assets with an efficient cache policy
47 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
JavaScript execution time
0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid serving legacy JavaScript to modern browsers
Potential savings of 42 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Time to Interactive
1.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid long main-thread tasks
1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid an excessive DOM size
1,063 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Initial server response time was short
Root document took 480 ms
Keep the server response time for the main document short because all other requests depend on it
Properly size images
Potential savings of 19 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
Cumulative Layout Shift
0.711
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid non-composited animations
8 animated elements found
Animations which are not composited can be janky and increase CLS
Keep request counts low and transfer sizes small
162 requests • 4,159 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Serve images in next-gen formats
Potential savings of 618 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Eliminate render-blocking resources
Potential savings of 700 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
Reduce unused CSS
Potential savings of 54 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Speed Index
4.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Mobile
Avoid an excessive DOM size
988 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First Contentful Paint
3.6 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce JavaScript execution time
6.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short
Root document took 420 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce unused CSS
Potential savings of 44 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Minimize main-thread work
12.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
Avoid enormous network payloads
Total size was 3,707 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve static assets with an efficient cache policy
45 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint
15.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Max Potential First Input Delay
440 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minify JavaScript
Potential savings of 19 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,430 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Serve images in next-gen formats
Potential savings of 680 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Tap targets are not sized appropriately
84% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Avoid non-composited animations
8 animated elements found
Animations which are not composited can be janky and increase CLS
First Contentful Paint (3G)
7230 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Reduce unused JavaScript
Potential savings of 738 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Speed Index
11.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
Avoid serving legacy JavaScript to modern browsers
Potential savings of 42 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Eliminate render-blocking resources
Potential savings of 3,380 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Cumulative Layout Shift
0.944
Cumulative Layout Shift measures the movement of visible elements within the viewport
Efficiently encode images
Potential savings of 219 KiB
Optimized images load faster and consume less cellular data
Time to Interactive
20.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Total Blocking Time
3,150 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Enable text compression
Potential savings of 109 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Meaningful Paint
4.3 s
First Meaningful Paint measures when the primary content of a page is visible
Document uses legible font sizes
90.23% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Avoid chaining critical requests
56 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Keep request counts low and transfer sizes small
152 requests • 3,707 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Speed And Optimization Tips
Only Registered Users
Sign up for see all features and reviews about this site
Login
Alexa Rank
Only Registered Users
Sign up for see all features and reviews about this site
Login
Domain Available
Domain (TDL) and Typo
Status
faccia.co
Available
Buy Now!
faccia.us
Available
Buy Now!
faccia.com
Available
Buy Now!
faccia.org
Available
Buy Now!
faccia.net
Available
Buy Now!
fccia.pt
Available
Buy Now!
raccia.pt
Available
Buy Now!
vaccia.pt
Available
Buy Now!
Information Server
Only Registered Users
Sign up for see all features and reviews about this site
Login
Login/Register
Shortcuts
Shortcut traffic
Shortcut tips
Shortcut alexa
Shortcut server
Shortcut meta
Shortcut authority
Shortcut technologies
Shortcut pagespeed
Shortcut pagespeed_stats
Shortcut social
Shortcut domain_available
Pages
Politica de Privacidade
Contact
Latest Updated Sites
Top Sites
Languages
English
Espanhol
French
Português
...
Please wait
Starting process...