Your Website Score is

Similar Ranking

1
MEGAPHONE - LOJA ONLINE DE T-SHIRTS PERSONALIZADAS
megaphone.pt

Latest Sites

31
ORTHOPETCARE
orthopetcare.pt
19
MYIEVOLUTION - TERAPIA ONLINE - TERAPIA ONLINE %
myievolution.com
35
TECHENET - NOTÍCIAS E INFORMAÇÃO DE TECNOLOGIA
techenet.com
19
RAG TAILORS - FARDAS E UNIFORMES À IMAGEM DO SEU NEGÓCIO
ragtailors.com
14
11
KID TO KID ONLINE
kidtokidonline.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 megaphone.pt Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 58%
Best Practices Desktop Score 64%
SEO Desktop Score 73%
Progressive Web App Desktop Score 33%
Performance Mobile Score 36%
Best Practices Mobile Score 57%
SEO Mobile Score 76%
Progressive Web App Mobile Score 32%
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

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
Efficiently encode images Potential savings of 678 KiB
Optimized images load faster and consume less cellular data
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 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.25
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
First CPU Idle 1.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/).
Remove unused CSS Potential savings of 12 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
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
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
Minimize third-party usage Third-party code blocked the main thread for 50 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
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
Minimizes main-thread work 1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 4.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy 31 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid long main-thread tasks 2 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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid enormous network payloads Total size was 4,708 KiB
Large network payloads cost users real money and are highly correlated with long load times
Keep request counts low and transfer sizes small 83 requests • 4,708 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
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
Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 800 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused JavaScript Potential savings of 175 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minify JavaScript Potential savings of 15 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 17 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
Time to Interactive 4.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Properly size images Potential savings of 769 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Includes front-end JavaScript libraries with known security vulnerabilities 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid an excessive DOM size 1,085 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)
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Preload key requests Potential savings of 670 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Serve images in next-gen formats Potential savings of 2,879 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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 20.0 s
A fast page load over a cellular network ensures a good mobile user experience

Mobile

Mobile Screenshot
Avoid chaining critical requests 17 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
Document uses legible font sizes 99.88% 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
Largest Contentful Paint 17.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove unused JavaScript Potential savings of 175 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Keep request counts low and transfer sizes small 82 requests • 4,694 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Meaningful Paint 3.2 s
First Meaningful Paint measures when the primary content of a page is visible
Defer offscreen images Potential savings of 282 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Avoid enormous network payloads Total size was 4,694 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 1.476
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Contentful Paint (3G) 6570 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Efficiently encode images Potential savings of 748 KiB
Optimized images load faster and consume less cellular data
Time to Interactive 17.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint 3.2 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time 270 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First CPU Idle 5.8 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/).
Serve static assets with an efficient cache policy 31 resources found
A long cache lifetime can speed up repeat visits to your page
Estimated Input Latency 30 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
Includes front-end JavaScript libraries with known security vulnerabilities 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Reduce JavaScript execution time 1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats Potential savings of 2,807 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
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 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
Minify JavaScript Potential savings of 15 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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
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
Speed Index 10.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimize main-thread work 3.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Eliminate render-blocking resources Potential savings of 2,410 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Preload key requests Potential savings of 1,140 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Page load is not fast enough on mobile networks Interactive at 17.2 s
A fast page load over a cellular network ensures a good mobile user experience
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Reduce the impact of third-party code Third-party code blocked the main thread for 330 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
Avoid an excessive DOM size 1,085 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 570 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 260 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Tap targets are not sized appropriately 93% 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
Remove unused CSS Potential savings of 12 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.

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

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Only Registered Users

Sign up for see all features and reviews about this site

Login