Your Website Score is

Latest Sites

13
FREDERICO LOPES - WORDPRESS SEO
fredericolopes.com
19
HOME - ATMOSFERASTORE
atmosferastore.com
7
INDEX OF /
ceramileao.com
26
DUDEK PORTUGAL – ASAS DUDEK
dudek.pt
19
FOTOGRAFIAS, APENAS
fotografiasapenas.blogspot.pt
14
CAIXIPRONTO – ALUMÍNIOS E PVC
caixipronto.pt
19
VIDEOLIGHT - VIDEO PORTEIRO, TELEFONES DE PORTA, E INTERCOMUNICADORES
videolight.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

1 ergobrilho.pt Last Updated: 1 week

Success 47% of passed verification steps
Warning 15% of total warning
Errors 38% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 87%
Best Practices Desktop Score 79%
SEO Desktop Score 80%
Progressive Web App Desktop Score 30%
Performance Mobile Score 57%
Best Practices Mobile Score 71%
SEO Mobile Score 67%
Progressive Web App Mobile Score 29%
Page Authority Authority 13%
Domain Authority Domain Authority 3%
Moz Rank 1.3/10
Bounce Rate Rate 0%
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 20 Characters
http://ergobrilho.pt
Google Preview Your look like this in google search result
ergobrilho.pt
http://ergobrilho.pt
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~1 B
Code Size: ~NAN B
Text Size: ~1 B Ratio: 100.00%

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

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Keep request counts low and transfer sizes small 53 requests • 1,210 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Includes front-end JavaScript libraries with known security vulnerabilities 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
First CPU Idle 1.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
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
Avoids an excessive DOM size 389 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)
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
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Eliminate render-blocking resources Potential savings of 1,100 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid serving legacy JavaScript to modern browsers Potential savings of 21 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
Cumulative Layout Shift 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimizes main-thread work 0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads Total size was 1,210 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve static assets with an efficient cache policy 46 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Properly size images Potential savings of 22 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Time to Interactive 1.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve images in next-gen formats Potential savings of 535 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Initial server response time was short Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Does not use HTTPS 53 insecure requests 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 servedover 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
Remove unused JavaScript Potential savings of 91 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Avoid chaining critical requests 19 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
Enable text compression Potential savings of 235 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Mobile

Mobile Screenshot
Enable text compression Potential savings of 235 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Speed Index 4.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Largest Contentful Paint 7.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids enormous network payloads Total size was 1,209 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
Serve images in next-gen formats Potential savings of 535 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Time to Interactive 6.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Includes front-end JavaScript libraries with known security vulnerabilities 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Remove unused JavaScript Potential savings of 91 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Contentful Paint (3G) 9317 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
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
First Contentful Paint 4.3 s
First Contentful Paint marks the time at which the first text or image is painted
First Meaningful Paint 4.5 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids an excessive DOM size 389 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)
Does not use HTTPS 53 insecure requests 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 servedover 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
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
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Max Potential First Input Delay 110 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Serve static assets with an efficient cache policy 46 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Eliminate render-blocking resources Potential savings of 3,880 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests 19 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
Avoid serving legacy JavaScript to modern browsers Potential savings of 21 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
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
Cumulative Layout Shift 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Keep request counts low and transfer sizes small 53 requests • 1,209 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

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
ergobrilho.co Available Buy Now!
ergobrilho.us Available Buy Now!
ergobrilho.com Available Buy Now!
ergobrilho.org Available Buy Now!
ergobrilho.net Available Buy Now!
egobrilho.pt Available Buy Now!
xrgobrilho.pt Available Buy Now!
drgobrilho.pt Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server