Your Website Score is

Similar Ranking

14
VISTOREPRO – A SUA LOJA ONLINE
vistorepro.com
14
GRANDE CAMPO – LOJA ONLINE – COMPRAR FLORES ONLINE
grandecampo.pt
14
EXCLUSIVE VILLA CASCAIS – THE BEST HOUSES TO SELL OR BUY IN CASCAIS
exclusivevillacascais.com
14
GOLDEN SKY JETS | EXECUTIVE AVIATION
goldenskyjets.com
14
ADVOGADO | BALCÃO DO SOLICITADOR - VILA NOVA DE MIL FONTES | BEJA
tc-juridico.pt
14
HOME | BRANDQUEEN GROUP
brandqc.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

14 lojaloveme.com.br Last Updated: 4 weeks

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

Desktop

Mobile

Performance Desktop Score 56%
Best Practices Desktop Score 93%
SEO Desktop Score 83%
Progressive Web App Desktop Score 45%
Performance Mobile Score 5%
Best Practices Mobile Score 93%
SEO Mobile Score 84%
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

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
Estimated Input Latency 40 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
Remove unused JavaScript Potential savings of 183 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
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 long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint 1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Cumulative Layout Shift 0.492
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid enormous network payloads Total size was 3,180 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
Avoid non-composited animations 92 animated elements found
Animations which are not composited can be janky and increase CLS
Speed Index 3.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.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/).
Minimize third-party usage Third-party code blocked the main thread for 160 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
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 large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize main-thread work 2.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources Potential savings of 580 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Enable text compression Potential savings of 43 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Properly size images Potential savings of 587 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Serve static assets with an efficient cache policy 136 resources found
A long cache lifetime can speed up repeat visits to your page
Use HTTP/2 1 request not served via HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing
Defer offscreen images Potential savings of 53 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid chaining critical requests 105 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 an excessive DOM size 1,627 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)
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
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
Total Blocking Time 350 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive 3.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve images in next-gen formats Potential savings of 1,076 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
Keep request counts low and transfer sizes small 155 requests • 3,180 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Remove unused CSS Potential savings of 249 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
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce initial server response time Root document took 790 ms
Keep the server response time for the main document short because all other requests depend on it

Mobile

Mobile Screenshot
Enable text compression Potential savings of 43 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
First Contentful Paint 5.9 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce JavaScript execution time 4.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Serve static assets with an efficient cache policy 123 resources found
A long cache lifetime can speed up repeat visits to your page
Properly size images Potential savings of 420 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Max Potential First Input Delay 1,080 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid enormous network payloads Total size was 2,804 KiB
Large network payloads cost users real money and are highly correlated with long load times
Initial server response time was short Root document took 300 ms
Keep the server response time for the main document short because all other requests depend on it
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
Document uses legible font sizes 98.39% 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
First CPU Idle 15.9 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/).
First Meaningful Paint 5.9 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize main-thread work 10.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce the impact of third-party code Third-party code blocked the main thread for 1,530 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 872 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
First Contentful Paint (3G) 12330 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Eliminate render-blocking resources Potential savings of 4,130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Estimated Input Latency 470 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
Cumulative Layout Shift 0.711
Cumulative Layout Shift measures the movement of visible elements within the viewport
Speed Index 10.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive 16.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint 10.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Avoid an excessive DOM size 1,533 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)
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
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
Defer offscreen images Potential savings of 73 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Remove unused CSS Potential savings of 249 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 chaining critical requests 106 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
Tap targets are not sized appropriately 85% 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
Keep request counts low and transfer sizes small 147 requests • 2,804 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid non-composited animations 75 animated elements found
Animations which are not composited can be janky and increase CLS
Total Blocking Time 2,560 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused JavaScript Potential savings of 183 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
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