Your Website Score is

Similar Ranking

31
DISCOVERY FOR YOU TOURS – RESERVAS ONLINE PARA TOURS PERSONALIZADOS ENTRE LISBOA, SINTRA E FÁTIMA
discoveryforyou.com
31
URMET PORTUGAL - INSTALAÇÃO, REPARAÇÃO DE VIDEOPORTEIROS
urmet.pt
31
PUZZLE FAMILY - VESTIMOS TODA FAMILIA - 100% PORTUGUESA
puzzlefamily.pt
31
ALBUFEIRA BOAT TRIPS TO THE MOST BEAUTIFUL CAVES IN THE ALGARVE
albufeiraboattrips.com
31
DESMATAÇÃO E LIMPEZA DE TERRENOS
desmatarportugal.pt
31
GM - INFORMÁTICA E CONSUMÍVEIS - TINTEIROS E TONER
gilmonteiro.pt
31
PAULO SALGADO – BRANDING & COMUNICAÇÃO
paulosalgado.com

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

31 orthopetcare.pt Last Updated: 4 days

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

Desktop

Mobile

Performance Desktop Score 61%
Best Practices Desktop Score 87%
SEO Desktop Score 92%
Progressive Web App Desktop Score 45%
Performance Mobile Score 9%
Best Practices Mobile Score 87%
SEO Mobile Score 91%
Progressive Web App Mobile Score 50%
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
Initial server response time was short Root document took 190 ms
Keep the server response time for the main document short because all other requests depend on it
Serve images in next-gen formats Potential savings of 457 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
Time to Interactive 3.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Keep request counts low and transfer sizes small 88 requests • 3,612 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minimize third-party usage Third-party code blocked the main thread for 40 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 CPU Idle 3.4 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/).
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 serving legacy JavaScript to modern browsers Potential savings of 26 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
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
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
Avoid enormous network payloads Total size was 3,612 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Enable text compression Potential savings of 1,163 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Remove unused JavaScript Potential savings of 965 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted
Remove unused CSS Potential savings of 971 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 long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.679
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 3.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids an excessive DOM size 572 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)
Serve static assets with an efficient cache policy 21 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources Potential savings of 950 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Properly size images Potential savings of 66 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid chaining critical requests 7 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 large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Max Potential First Input Delay 120 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task

Mobile

Mobile Screenshot
Eliminate render-blocking resources Potential savings of 5,680 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Minimize main-thread work 5.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Time to Interactive 24.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint (3G) 15434 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Cumulative Layout Shift 0.318
Cumulative Layout Shift measures the movement of visible elements within the viewport
Total Blocking Time 950 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce the impact of third-party code Third-party code blocked the main thread for 300 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
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
Properly size images Potential savings of 147 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Keep request counts low and transfer sizes small 103 requests • 3,919 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
First Meaningful Paint 6.9 s
First Meaningful Paint measures when the primary content of a page is visible
Serve images in next-gen formats Potential savings of 457 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 enormous network payloads Total size was 3,919 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 7 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
Remove unused CSS Potential savings of 976 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
Defer offscreen images Potential savings of 67 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First CPU Idle 19.3 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 element 1 element found
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy 21 resources found
A long cache lifetime can speed up repeat visits to your page
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 17.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Tap targets are not sized appropriately 86% 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 JavaScript Potential savings of 976 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Contentful Paint 6.9 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 13.0 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
Document uses legible font sizes 81.57% 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
Estimated Input Latency 60 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
Max Potential First Input Delay 340 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Reduce initial server response time Root document took 1,080 ms
Keep the server response time for the main document short because all other requests depend on it
Enable text compression Potential savings of 1,163 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid serving legacy JavaScript to modern browsers Potential savings of 26 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 non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
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
Reduce JavaScript execution time 2.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids an excessive DOM size 573 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)

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