Your Website Score is
19 ezperito.com Last Updated: 1 month
Success
54% of passed verification steps
Warning
23% of total warning
Errors
23% of total errors, require fast action
Share
Desktop
Mobile
Page Authority
Authority 0%
Domain Authority
Domain Authority 0%
Moz Rank
0.0/10
Bounce Rate
Rate 0%
charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
52 Characters
PERÍCIA FORENSE | EDUARDO ZOCCHI - EZ PERITO| BRASIL
Meta Description
247 Characters
Perito atuante há mais de 30 anos, em diversas áreas das ciências forenses, tecnologia; incluindo engenharia, áudio, vídeo e imagens; acidentes com veículos, embarcações, aeronaves, grafotécnica e documentoscopia, etc.
EZ Perito - Perícia Forense
Effective URL
24 Characters
https://www.ezperito.com
Excerpt
Page content
Perícia Forense | Eduardo Zocchi - EZ Perito| Brasil
top of page“A prova pericial é, dentre as provas produzidas na persecu&cc...
Google Preview
Your look like this in google search result
PERÍCIA FORENSE | EDUARDO ZOCCHI - EZ PERITO| BRASIL
https://www.ezperito.com
Perito atuante há mais de 30 anos, em diversas áreas das ciências forenses, tecnologia; incluindo engenharia, áudio, vídeo e imagens; acidentes com ve
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~417.5 KB
Code Size: ~61.36 KB
Text Size: ~356.14 KB Ratio: 85.30%
Social Data
Estimation Traffic and Earnings
8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly
Desktop
Remove duplicate modules in JavaScript bundles
Est savings of 99 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Serve static assets with an efficient cache policy
102 resources found
A long cache lifetime can speed up repeat visits to your page
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
Reduce unused CSS
Est savings of 179 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Cumulative Layout Shift
0.03
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce unused JavaScript
Est savings of 610 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Initial server response time was short
Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts
4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Avoid long main-thread tasks
6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Largest Contentful Paint
1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Improve image delivery
Est savings of 639 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Minimize main-thread work
2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive
3.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
User Timing marks and measures
146 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Properly size images
Est savings of 50 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Total Blocking Time
120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated
JavaScript execution time
1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Duplicated JavaScript
Est savings of 155 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Use video formats for animated content
Est savings of 616 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Largest Contentful Paint element
1,930 ms
This is the largest contentful element painted within the viewport
Avoids an excessive DOM size
307 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)
Enable text compression
Est savings of 2 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize third-party usage
Third-party code blocked the main thread for 210 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 enormous network payloads
Total size was 3,515 KiB
Large network payloads cost users real money and are highly correlated with long load times
Network Round Trip Times
10 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
Uses third-party cookies
2 cookies found
Third-party cookies may be blocked in some contexts
Avoid serving legacy JavaScript to modern browsers
Est savings of 2 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Minify JavaScript
Est savings of 47 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Use efficient cache lifetimes
Est savings of 67 KiB
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay
130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Mobile
Speed Index
7.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid enormous network payloads
Total size was 3,368 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce JavaScript execution time
2.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused CSS
Est savings of 179 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers
Est savings of 2 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Uses third-party cookies
2 cookies found
Third-party cookies may be blocked in some contexts
Total Blocking Time
570 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Improve image delivery
Est savings of 842 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Remove duplicate modules in JavaScript bundles
Est savings of 120 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Use efficient cache lifetimes
Est savings of 67 KiB
A long cache lifetime can speed up repeat visits to your page
Reduce the impact of third-party code
Third-party code blocked the main thread for 600 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
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
Duplicated JavaScript
Est savings of 227 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Server Backend Latencies
10 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
Est savings of 622 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Minify JavaScript
Est savings of 47 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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
Serve static assets with an efficient cache policy
102 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint
20.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Max Potential First Input Delay
250 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Cumulative Layout Shift
0.057
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint element
20,910 ms
This is the largest contentful element painted within the viewport
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 70 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce unused JavaScript
Est savings of 659 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid large layout shifts
1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
First Contentful Paint
3.3 s
First Contentful Paint marks the time at which the first text or image is painted
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
User Timing marks and measures
150 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Avoids an excessive DOM size
336 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)
Use video formats for animated content
Est savings of 616 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Time to Interactive
21.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Congratulations! Your title is 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
Congratulations! You not have broken links
View links
| First 8 Links | Relationship | HTTP Status |
| EZ Perito | Internal Link | 200 |
| Referências | Internal Link | 200 |
| Perícias | Internal Link | 200 |
| Na mídia / Palestras | Internal Link | 200 |
| Cursos | Internal Link | 200 |
| Artigos e Textos Técnicos | Internal Link | 200 |
| Contato | Internal Link | 200 |
| https://www.ezperito.com/equipe | Internal Link | 200 |
Alexa Rank
99,999,999
Global Rank99,999,999
-
Traffic
Search
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| ezperito.co | Available |
| ezperito.us | Available |
| ezperito.com | Already Registered |
| ezperito.org | Available |
| ezperito.net | Available |
| eperito.com | Already Registered |
| xzperito.com | Available |
| dzperito.com | Available |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
content-type: text/html; charset=UTF-8
link: ; rel=preconnect; crossorigin;,; rel=preconnect;,; rel=preconnect; crossorigin;,; rel=preconnect;,; rel=preconnect; crossorigin;,
html-cacheable: true
etag: W/"a82badfec8597c09bb0c11c0e9c3635e"
content-language: en-US
strict-transport-security: max-age=86400
cache-control: public,max-age=0,must-revalidate
server: Pepyaka
x-content-type-options: nosniff
content-encoding: gzip
accept-ranges: bytes
date: Mon, 23 Jun 2025 03:40:13 GMT
age: 561430
x-served-by: cache-yyz4557-YYZ
x-cache: HIT
vary: Accept-Encoding
server-timing: cache;desc=hit, varnish;desc=hit_hit, dc;desc=fastly_g
set-cookie: ssr-caching=cache#desc=hit#varnish=hit_hit#dc#desc=fastly_g; max-age=20
x-wix-request-id: 1750650013.922452235934694711
x-seen-by: yvSunuo/8ld62ehjr5B7kA==
via: 1.1 google
glb-x-seen-by: bS8wRlGzu0Hc+WrYuHB8QIg44yfcdCMJRkBoQ1h6Vjc=
Transfer-Encoding: chunked
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000