Your Website Score is

Similar Ranking

22
EMPRESAS DE MUDANÇAS NACIONAIS OU INTERNACIONAIS 24 HORAS
mudancas.pt
22
ILUMINAçãO, MATERIAL ELéCTRICO | ELECTROMINOR
electrominor.pt
22
MULTI TIENDA ONLINE
justdeal.es
22
HOST WISE | GERIMOS E RENTABILIZAMOS O SEU IMÓVEL
hostwise.pt
22
SUPORTE INFORMÁTICO - TECNOLOGIA, WEBSITES E SEO | RAUL SILVA
raulcnsilva.com
22
CARLOS DINIZ | CONSULTOR DE MARKETING DIGITAL
carlosdiniz.pt
22
CUPÕES.ONLINE: CÓDIGOS DE DESCONTO E PROMOÇÕES
cupoes.online

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

PHP
Programming Languages
Google Font API
Font Scripts
WordPress
CMS
Apache
Web Servers
Font Awesome
Font Scripts
Nginx
Web Servers
jQuery
JavaScript Frameworks
Yoast SEO
SEO
WooCommerce
Ecommerce
Google Tag Manager
Tag Managers

22 wellclean.pt Last Updated: 3 weeks

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

Desktop

Mobile

Performance Desktop Score 82%
Best Practices Desktop Score 79%
SEO Desktop Score 100%
Progressive Web App Desktop Score 26%
Performance Mobile Score 30%
Best Practices Mobile Score 79%
SEO Mobile Score 98%
Progressive Web App Mobile Score 29%
Page Authority Authority 16%
Domain Authority Domain Authority 10%
Moz Rank 1.6/10
Bounce Rate Rate 0%
Title Tag 60 Characters
WELLCLEAN LIMPEZAS PROFISSIONAIS, DOMÉSTICAS E EMPRESARIAIS!
Meta Description 182 Characters
A WellCLEAN é uma empresa de LIMPEZA, com larga experiencia, fundada em 2008 a prestar serviços de Limpeza Profissional, "Regulares e Ocasionais", na área da Grande Lisboa.
Effective URL 24 Characters
https://www.wellclean.pt
Excerpt Page content
WellClean Limpezas Profissionais, Domésticas e Empresariais! Skip to content  ...
Keywords Cloud Density
limpeza59 limpezas26 serviços22 desinfeção13 gallery12 vidros7 wellclean7 têxteis7 alcatifas6 sofás6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
limpeza 59
limpezas 26
serviços 22
desinfeção 13
gallery 12
vidros 7
wellclean 7
têxteis 7
alcatifas 6
sofás 6
Google Preview Your look like this in google search result
WELLCLEAN LIMPEZAS PROFISSIONAIS, DOMÉSTICAS E EMPRESARIAIS!
https://www.wellclean.pt
A WellCLEAN é uma empresa de LIMPEZA, com larga experiencia, fundada em 2008 a prestar serviços de Limpeza Profissional, "Regulares e Ocasionais&
Robots.txt File Detected
http://wellclean.pt/robots.txt
Sitemap.xml File Detected
http://wellclean.pt/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~67.57 KB
Code Size: ~55.08 KB
Text Size: ~12.5 KB Ratio: 18.49%

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
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
Estimated Input Latency 20 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
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Serve images in next-gen formats Potential savings of 33 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
Avoids an excessive DOM size 743 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 1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Preload key requests Potential savings of 830 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 on simulated mobile network at 10.9 s
A fast page load over a cellular network ensures a good mobile user experience
Cumulative Layout Shift 0.373
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid serving legacy JavaScript to modern browsers Potential savings of 17 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
Remove unused CSS Potential savings of 121 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
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
Properly size images Potential savings of 36 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
JavaScript execution time 0.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused JavaScript Potential savings of 226 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Eliminate render-blocking resources Potential savings of 690 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve static assets with an efficient cache policy 22 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Total Blocking Time 170 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive 2.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Reduce initial server response time Root document took 770 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads Total size was 1,228 KiB
Large network payloads cost users real money and are highly correlated with long load times
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 chaining critical requests 9 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
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
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
Keep request counts low and transfer sizes small 43 requests • 1,228 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 2.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/).
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
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
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

Mobile

Mobile Screenshot
Serve static assets with an efficient cache policy 11 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.391
Cumulative Layout Shift measures the movement of visible elements within the viewport
Estimated Input Latency 230 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 an excessive DOM size 739 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)
First Meaningful Paint 4.1 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid chaining critical requests 9 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 long main-thread tasks 16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimize main-thread work 4.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Preload key requests Potential savings of 3,180 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Tap targets are not sized appropriately 87% 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
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
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
Speed Index 5.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Remove unused CSS Potential savings of 121 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
Remove unused JavaScript Potential savings of 226 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids enormous network payloads Total size was 1,133 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint (3G) 8790 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Page load is not fast enough on mobile networks Interactive at 10.1 s
A fast page load over a cellular network ensures a good mobile user experience
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
Reduce JavaScript execution time 3.3 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
First CPU Idle 9.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/).
Time to Interactive 10.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint 5.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid serving legacy JavaScript to modern browsers Potential savings of 17 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
Properly size images Potential savings of 82 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Total Blocking Time 980 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Keep request counts low and transfer sizes small 33 requests • 1,133 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Reduce the impact of third-party code Third-party code blocked the main thread for 830 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
Reduce initial server response time Root document took 660 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 610 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.
Serve images in next-gen formats Potential savings of 33 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 4.1 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Potential savings of 3,120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

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
wellclean.co Already Registered
wellclean.us Available Buy Now!
wellclean.com Available Buy Now!
wellclean.org Available Buy Now!
wellclean.net Already Registered
wllclean.pt Available Buy Now!
zellclean.pt Available Buy Now!
sellclean.pt Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/2 200 
server: nginx
date: Mon, 04 Jan 2021 03:06:05 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
x-pingback: https://www.wellclean.pt/xmlrpc.php
link: ; rel="https://api.w.org/", ; rel="alternate"; type="application/json", ; rel=shortlink
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
content-encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A wellclean.pt 104.248.94.228 IN 32
NS wellclean.pt ns7.mydnspt.net IN 198
NS wellclean.pt ns1.mydnspt.net IN 198
NS wellclean.pt ns2.mydnspt.net IN 198
NS wellclean.pt ns8.mydnspt.net IN 198
MX wellclean.pt mail.wellclean.pt IN 300
TXT wellclean.pt v=spf1 +a +mx +ip4:109.71.43.153 +ip4:109.71.43.137 +ip4:109.71.40.22 +ip4:50.59.99.187 +ip4:173.225.101.12 +include:_spf.cleanmx.pt +a:crab.apple.relay.mailchannels.net-all ~all IN 300

About Us

ProRank é uma Ferramenta desenvolvida por Frederico Lopes, um Freelancer de Lisboa, Especializado em WordPress e E-Commerce. Apaixonado por SEO e Conversões é também obcecado por novas ideias, e tecnologias, que tragam mais clientes para seu negócio.

Contact Info

Frederico Lopes
Rua do Sol ao Rato 45A
Lisboa
+351-937-712-822
info@fredericolopes.com

Follow Us

Facebook
Linkedin
Copyright 2019. ProRank - Todos os direitos reservados.
Languages | English Espanhol French Português