Your Website Score is

Similar Ranking

19
BE LAGOOM - DE MUJERES PARA MUJERES - MODA ONLINE
belagoom.com
19
AGALPORTOTEC,LDA
agalportotec.com
19
JOSÉ M. SILVA
josemsilva.pt
19
CÁTIA GUEDES - WEB DESIGN E MARKETING DIGITAL
catiaguedes.com
19
GRISP RESEARCH SOLUTIONS
grisp.pt
19
JOTI MENUISERIE ALU
joti.fr
19
TAXI4YOU MADEIRA
taxi4youmadeira.com

Latest Sites

36
ALUGUEL DE MATERIAL PARA FESTAS E EVENTOS EM ATIBAIA | NUESTRA FIESTA
nuestrafiesta.com.br
26
MARKETING DIGITAL BNEXT1 – APOIO MENSAL DE INVESTIMENTO ONLINE
so.bnext1.pt
27
REDUCE YOUR FOOTPRINT WHILE TRAVELING THE WORLD - NO FOOTPRINT NOMADS
nofootprintnomads.com
23
GERES CASAS | ALOJAMENTO BUNGALOWS CASAS DE FÉRIAS NO GERÊS
gerescasas.com
23
MONTES DE LABOREIRO - PARQUE NACIONAL PENEDA-GERÊS
montesdelaboreiro.pt
18
ANNA VIEIRA FOTOGRAFA – ANNA VIEIRA PRODUÇÕES – SERVIÇOS DE FOTOGRAFIA E IMAGEM
annavieirapt.com
17
INICIO - HOT MASSAGENS
hotmassagens.com

Top Technologies

Google Font API
Font Scripts
Apache
Web Servers
WordPress
CMS
Font Awesome
Font Scripts
WooCommerce
Ecommerce
Yoast SEO
SEO
Nginx
Web Servers
W3 Total Cache
Cache Tools

19 tmark.pt Last Updated: 3 weeks

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

Desktop

Mobile

Performance Desktop Score 54%
Best Practices Desktop Score 77%
SEO Desktop Score 100%
Progressive Web App Desktop Score 31%
Performance Mobile Score 14%
Best Practices Mobile Score 77%
SEO Mobile Score 100%
Progressive Web App Mobile Score 30%
Page Authority Authority 3%
Domain Authority Domain Authority 3%
Moz Rank 0.3/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 70 Characters
GOOGLE RESTAURANTES | TMARK - MARKETING DIGITAL - CRIAR LEADS | LISBOA
Meta Description 181 Characters
Tmark - Promoção site restaurante com sistema reservas Consiga clientes diretamente do Google Os nossos utilizadores beneficiam de mais 30% de reservas! Aproveite esta oportunidade!
Effective URL 20 Characters
https://www.tmark.pt
Excerpt Page content
Google Restaurantes | Tmark - Marketing Digital - Criar Leads | Lisboa ...
Keywords Cloud Density
google8 clientes8 seus5 mais5 reservas4 restaurante4 parceiros3 nossos2 crie2 setor2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
google 8
clientes 8
seus 5
mais 5
reservas 4
restaurante 4
parceiros 3
nossos 2
crie 2
setor 2
Google Preview Your look like this in google search result
GOOGLE RESTAURANTES | TMARK - MARKETING DIGITAL - CRIAR LEAD
https://www.tmark.pt
Tmark - Promoção site restaurante com sistema reservas Consiga clientes diretamente do Google Os nossos utilizadores beneficiam de mais 30% de reserva
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~537.25 KB
Code Size: ~73.77 KB
Text Size: ~463.48 KB Ratio: 86.27%

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
Reduce server response times (TTFB) Root document took 950 ms
Time To First Byte identifies the time at which your server sends a response
Reduce the impact of third-party code Third-party code blocked the main thread for 1,390 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
Total Blocking Time 1,090 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 3.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 134 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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 553 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.6 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).
Avoid enormous network payloads Total size was 4,199 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 5.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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 8 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 an excessive DOM size 474 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)
Minify JavaScript Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 163 requests • 4,200 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 73 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 610 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 5.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 25.8 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 190 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
Minify CSS Potential savings of 3 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 49 KB
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
Serve images in next-gen formats Potential savings of 534 KB
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
User Timing marks and measures 88 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Mobile

Mobile Screenshot
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 an excessive DOM size 434 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)
Preload key requests Potential savings of 5,970 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 4.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 168 requests • 3,947 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 77 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 2,930 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 26.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Page load is not fast enough on mobile networks Interactive at 26.4 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 1,960 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 Contentful Paint (3G) 9415 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minify CSS Potential savings of 3 KB
Minifying CSS files can reduce network payload sizes
Tap targets are sized appropriately 100% 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
Document uses legible font sizes 97.3% 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
Remove unused CSS Potential savings of 50 KB
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
Serve images in next-gen formats Potential savings of 498 KB
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
User Timing marks and measures 82 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Reduce server response times (TTFB) Root document took 870 ms
Time To First Byte identifies the time at which your server sends a response
Reduce the impact of third-party code Third-party code blocked the main thread for 9,540 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
Total Blocking Time 7,070 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 14.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 3 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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 538 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 10.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 23.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).
Avoid enormous network payloads Total size was 3,946 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 22.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.3 s
First Contentful Paint marks the time at which the first text or image is painted

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
tmark.co Already Registered
tmark.us Already Registered
tmark.com Available Buy Now!
tmark.org Available Buy Now!
tmark.net Already Registered
tark.pt Available Buy Now!
vmark.pt Available Buy Now!
gmark.pt Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Wed, 11 Mar 2020 09:23:43 GMT
Content-Type: text/html;charset=utf-8
Connection: keep-alive
content-language: en
link: ; rel=preconnect; crossorigin,; rel=preconnect; crossorigin,; rel=preconnect;,; rel=preload; as=script;,; rel=preload; as=script ; crossorigin=anonymous;,; rel=preload; as=script ; crossorigin=anonymous;,; rel=preconnect; crossorigin;,; rel=preload; as=script ; crossorigin=anonymous;
pragma: no-cache
Age: 1
Set-Cookie: ssr-caching="cache,desc=hit,varnish=hit, dc,desc=84";Version=1;Expires=Wed, 11-Mar-2020 09:24:01 GMT;Max-Age=20
Server-Timing: cache;desc=hit, varnish;desc=hit, dc;desc=84
X-Seen-By: tFdftg60YAKRbpNz6vsYOw==,sHU62EDOGnH2FBkJkG/Wx8EeXWsWdHrhlvbxtlynkVgaURv9Mpw1cLG9pxQMvzc/,2d58ifebGbosy5xc+FRali+5JVsJlCHJJLwuiffEsy1H7zzBUOtLxIwnweWItAD9bJJKhz0ej6j+qD5rtHbm3A==,2UNV7KOq4oGjA5+PKsX47JRa/JYjcpnMLX0Jx8Ii4W8=
Cache-Control: no-cache, no-store,no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Wix-Request-Id: 1583918623.060225817068118323
Content-Encoding: gzip
Set-Cookie: TS01e85bed=0141ccf4853032cab50828aac52acfd60ebb9f2c0a3bbd26b3217cd22140e9f1be5ca61ac783528de494a1fe8f3cb456e12f0c0321; Path=/
Transfer-Encoding: chunked
DNS Records DNS Resource Records associated with a hostname
View DNS Records