Your Website Score is

Similar Ranking

89
GOOGLE
google.pt
85
PÚBLICO — PENSE BEM, PENSE PÚBLICO
publico.pt

Latest Sites

14
TRAFFIC-SUBMIT - WEBSITE TRAFFIC IN REAL TIME.
traffic-submit.com
31
PIM PAM PUM - HAMBURGUERIA PRAIA DA ROCHA
hamburgueriapraiadarocha.com
10
ZONTES – ZONTES PORTUGAL
zontes.pt
14
WEBMÓVEL
webmovel.pt
22
QUINTA DO RAJO – A QUINTA DO RAJO É A SEDE DA ESCOLA INTERNACIONAL DE KARAM KRIYA.
quinta-do-rajo.pt
89
GOOGLE
google.pt

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
Apache
Web Servers
Font Awesome
Font Scripts
Nginx
Web Servers
Yoast SEO
SEO
WooCommerce
Ecommerce
Google Tag Manager
Tag Managers

89 google.pt Last Updated: 2 weeks

Success 54% of passed verification steps
Warning 23% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 100%
Best Practices Desktop Score 80%
SEO Desktop Score 82%
Progressive Web App Desktop Score 36%
Performance Mobile Score 90%
Best Practices Mobile Score 80%
SEO Mobile Score 85%
Progressive Web App Mobile Score 58%
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

Desktop Screenshot
Avoid multiple page redirects Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded
Minimizes main-thread work 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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 chaining critical requests 1 chain 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
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused JavaScript Potential savings of 58 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoids an excessive DOM size 314 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)
Largest Contentful Paint 0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 0.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Initial server response time was short Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids enormous network payloads Total size was 158 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 0.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
Keep request counts low and transfer sizes small 12 requests • 158 KiB
To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Mobile Screenshot
Avoids an excessive DOM size 312 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)
Time to Interactive 4.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint 2.3 s
First Meaningful Paint measures when the primary content of a page is visible
Initial server response time was short Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
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
Avoids enormous network payloads Total size was 191 KiB
Large network payloads cost users real money and are highly correlated with long load times
Document uses legible font sizes 100% 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
Minimizes main-thread work 0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Minimize third-party usage Third-party code blocked the main thread for 80 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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 serving legacy JavaScript to modern browsers Potential savings of 7 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 chaining critical requests 3 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
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted
First Contentful Paint (3G) 4590 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Keep request counts low and transfer sizes small 15 requests • 191 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Tap targets are sized appropriately 100% 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 multiple page redirects Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint 3.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused JavaScript Potential savings of 58 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

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
google.co Available Buy Now!
google.us Available Buy Now!
google.com Available Buy Now!
google.org Available Buy Now!
google.net Available Buy Now!
gogle.pt Available Buy Now!
toogle.pt Available Buy Now!
boogle.pt Available Buy Now!

Information Server

Only Registered Users

Sign up for see all features and reviews about this site

Login