Itusalgados.com.br - SEO Checker

Your Website Score is

Similar Ranking

fresks.se

giupemrdufq.html

colorlib.comgms

instagram.comhttps

kibfnuur.html

ads.php

wgpnzvlanen.html

Latest Sites

redtubes.rocks

xvideotop.com

YOUTUBE

youtu.be

gayxxx.tube

brightoneaglechauffeur.com

TROPOJA CONSTRUCTION LTD | TRUSTED CONSTRUCTION COMPANY IN LONDON

tropojaconstructionltd.co.uk

404 PAGE NOT FOUND

porntubes.casa

1 itusalgados.com.br Last Updated: 1 month

Success 40% of passed verification steps

Warning 7% of total warning

Errors 53% of total errors, require fast action

Mobile

Performance Desktop Score 69%

Best Practices Desktop Score 79%

SEO Desktop Score 83%

Progressive Web App Desktop Score 52%

Performance Mobile Score 42%

Best Practices Mobile Score 79%

SEO Mobile Score 84%

Progressive Web App Mobile Score 54%

Page Authority Authority 0%

Domain Authority Domain Authority 0%

Moz Rank 0.0/10

Bounce Rate Rate 0%

Title Tag 0 Characters

NO DATA

Meta Description 0 Characters

NO DATA

Effective URL 25 Characters

http://itusalgados.com.br

Google Preview Your look like this in google search result

itusalgados.com.br

http://itusalgados.com.br

Robots.txt File Detected

http://itusalgados.com.br/robots.txt

Sitemap.xml File Detected

http://itusalgados.com.br/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~1 B

Code Size: ~NAN B

Text Size: ~1 B Ratio: 100.00%

Estimation Traffic and Earnings

Unique Visits

Daily

Pages Views

Daily

Income

Daily

224

Unique Visits

Monthly

399

Pages Views

Monthly

Income

Monthly

2,592

Unique Visits

Yearly

4,704

Pages Views

Yearly

Income

Yearly

Desktop

Eliminate render-blocking resources Potential savings of 1,040 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 176 KiB

Serve images that are appropriately-sized to save cellular data and improve load time

First CPU Idle 1.7 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/).

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 an excessive DOM size 299 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 0 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

Cumulative Layout Shift 0.001

Cumulative Layout Shift measures the movement of visible elements within the viewport

Serve static assets with an efficient cache policy 41 resources found

A long cache lifetime can speed up repeat visits to your page

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

Time to Interactive 2.1 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Avoid chaining critical requests 29 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.

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

Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

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

Remove unused JavaScript Potential savings of 74 KiB

Remove unused JavaScript to reduce bytes consumed by network activity

Speed Index 4.3 s

Speed Index shows how quickly the contents of a page are visibly populated

Minimize third-party usage Third-party code blocked the main thread for 10 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

Avoids enormous network payloads Total size was 1,569 KiB

Large network payloads cost users real money and are highly correlated with long load times

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

Serve images in next-gen formats Potential savings of 281 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 Meaningful Paint 1.3 s

First Meaningful Paint measures when the primary content of a page is visible

Max Potential First Input Delay 50 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task

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

Initial server response time was short Root document took 330 ms

Keep the server response time for the main document short because all other requests depend on it

Largest Contentful Paint 2.3 s

Largest Contentful Paint marks the time at which the largest text or image is painted

Keep request counts low and transfer sizes small 64 requests • 1,569 KiB

To set budgets for the quantity and size of page resources, add a budget.json file

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 22 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

Minify JavaScript Potential savings of 12 KiB

Minifying JavaScript files can reduce payload sizes and script parse time

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

Mobile

First Meaningful Paint 4.9 s

First Meaningful Paint measures when the primary content of a page is visible

Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Time to Interactive 7.8 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Largest Contentful Paint 8.6 s

Largest Contentful Paint marks the time at which the largest text or image is painted

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport

Avoid large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page.

Minify JavaScript Potential savings of 12 KiB

Minifying JavaScript files can reduce payload sizes and script parse time

Reduce the impact of third-party code Third-party code blocked the main thread for 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

Avoid chaining critical requests 29 chains found

Defer offscreen images Potential savings of 92 KiB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to 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

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

Properly size images Potential savings of 6 KiB

Serve images that are appropriately-sized to save cellular data and improve load time

Cumulative Layout Shift 0.002

Cumulative Layout Shift measures the movement of visible elements within the viewport

Max Potential First Input Delay 240 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task

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

Remove unused JavaScript Potential savings of 75 KiB

Remove unused JavaScript to reduce bytes consumed by network activity

Keep request counts low and transfer sizes small 62 requests • 1,574 KiB

To set budgets for the quantity and size of page resources, add a budget.json file

First CPU Idle 6.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/).

Avoid long main-thread tasks 13 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

First Contentful Paint 4.0 s

First Contentful Paint marks the time at which the first text or image is painted

Avoids an excessive DOM size 298 elements

Tap targets are not sized appropriately 84% 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

Estimated Input Latency 50 ms

Remove unused CSS Potential savings of 22 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

Serve static assets with an efficient cache policy 41 resources found

A long cache lifetime can speed up repeat visits to your page

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

Minimize main-thread work 4.7 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

Avoid serving legacy JavaScript to modern browsers Potential savings of 17 KiB

Initial server response time was short Root document took 560 ms

Keep the server response time for the main document short because all other requests depend on it

Eliminate render-blocking resources Potential savings of 3,660 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

First Contentful Paint (3G) 7650 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Serve images in next-gen formats Potential savings of 281 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

Total Blocking Time 320 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

Reduce JavaScript execution time 1.8 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Avoids enormous network payloads Total size was 1,574 KiB

Large network payloads cost users real money and are highly correlated with long load times

Speed Index 12.5 s

Speed Index shows how quickly the contents of a page are visibly populated

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you

Title Website

Warning! Your title is not optimized

Description Website

Warning! Your description is not optimized

Robots.txt

Congratulations! Your site have a robots.txt file

Sitemap.xml

Congratulations! We've found a sitemap file for your website

SSL Secure

Congratulations! Your site have Support to HTTPS

Headings

Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines

Blacklist

Congratulations! Your site is not listed in a blacklist

W3C Validator

Warning! Your site have errors W3C

Accelerated Mobile Pages (AMP)

Warning! Your site not have AMP Version

Domain Authority

Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.

GZIP Compress

Warning! Your site not is compressed, this can make slower response for the visitors

Favicon

Congratulations! Your website appears to have a favicon.

Broken Links

Warning! You have broken links View links

First 4 Links	Relationship	HTTP Status
https://itusalgados.com.br	Internal Link	200
PEDIR ONLINE	Internal Link	200
ENCOMENDAS ONLINE	Internal Link	404
http://itusalgados.com.br	Internal Link	301

Alexa Rank

99,999,999

Global Rank

99,999,999

Traffic

Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	itusalgados.com.br	5.254.41.129	IN	14398
NS	itusalgados.com.br	ns4.saas-dfwbrasil.com	IN	21599
NS	itusalgados.com.br	ns2.saas-dfwbrasil.com	IN	21599
NS	itusalgados.com.br	ns3.saas-dfwbrasil.com	IN	21599
NS	itusalgados.com.br	ns1.saas-dfwbrasil.com	IN	21599
MX	itusalgados.com.br	itusalgados.com.br	IN	14399
TXT	itusalgados.com.br	google-site-verification=fXaaWYHW0UeYFQAJxl1JIcUOEiu1P4Z5MZymjFM6bwA	IN	14399
TXT	itusalgados.com.br	v=spf1 +a +mx +ip4:174.142.91.49 +ip4:192.175.106.199 ~all	IN	14399

Your Website Score is

Similar Ranking

Latest Sites

1 itusalgados.com.br Last Updated: 1 month

Desktop

Mobile

Estimation Traffic and Earnings

Desktop

Mobile

Speed And Optimization Tips

Alexa Rank

99,999,999

99,999,999

Information Server

About Us

Contact Info

Follow Us