Zelas.Com.Br - Info zelas.com.br

zelas.com.br receives about 4,264 unique visitors and 4,264 (1.00 per visitor) page views per day which should earn about $7.55/day from advertising revenue. Estimated site value is $5,509.61. According to Alexa Traffic Rank zelas.com.br is ranked number 594,111 in the world and 9.4E-5% of global Internet users visit it. Site is hosted in Seattle, Washington, 98109, United States and links to network IP address 13.226.15.31. This server supports HTTPS and HTTP/2.

About - zelas.com.br


Technologies used on Website

CDN
Amazon Cloudfront
Font Scripts
Google Font API
Web Servers
Nginx
Reverse proxies
Nginx
JavaScript Frameworks
Prototype
React
Analytics
Segment
PaaS
Amazon Web Services

zelas.com.br Profile

Description: Facilitamos sua compra de produtos essenciais.
Last update was 131 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with zelas.com.br in any way. Only publicly available statistics data are displayed.

How popular is zelas.com.br?

4.3K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
4,264
Monthly Unique Visitors:
102,336
Pages per Visit:
1.00
Daily Pageviews:
4,264
Alexa Rank:
594,111 visit alexa
Alexa Reach:
9.4E-5%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
Brazil 100.0%100.0%21987

Where do visitors go on this site?

Reach%Pageviews%PerUser
saude.zelas.com.br
100.00%100.00%1

Competitive Data

SEMrush
Domain:
  zelas.com.br
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is zelas.com.br?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
zelas.com.br
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
zelas.com.br
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much zelas.com.br can earn?

Daily Revenue:
$7.55
Monthly Revenue:
$226.50
Yearly Revenue:
$2,755.75
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Brazil 4,264$7.55

How much money do zelas.com.br lose due to Adblock?

Daily Revenue Loss:
$0.45
Monthly Revenue Loss:
$13.59
Yearly Revenue Loss:
$165.29
Daily Pageviews Blocked:
256
Monthly Pageviews Blocked:
7,675
Yearly Pageviews Blocked:
93,382
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Brazil 256$0.45

How much is zelas.com.br worth?

Website Value:
$5,509.61

+ Where is zelas.com.br hosted?

Server IP:
13.226.15.31
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Seattle
Washington, WA
98109
United States, US
 

Other sites hosted on 13.226.15.31

+ How fast does zelas.com.br load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
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. Learn more.
Tasks
Lists the toplevel main thread tasks that executed during page load.
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. Learn more.
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Minimizes main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Diagnostics
Collection of useful page vitals.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://zelas.com.br/
0 ms38 ms0 KB0 KB301text/html
https://zelas.com.br/
39 ms58 ms3 KB6 KB200text/htmlDocument
https://zelas.com.br/static/media/zelas-home.cbe466e0.svg
70 ms92 ms17 KB22 KB200image/svg+xmlImage
https://zelas.com.br/static/js/bundle.483d9fc0.js
70 ms163 ms91 KB282 KB200application/javascriptScript
https://cdn.segment.com/analytics.js/v1/v71cnjWvtktQ0qEKxfwPSRyzGsTBuiIa/analytics.min.js
73 ms98 ms56 KB286 KB200text/javascriptScript
https://fonts.googleapis.com/css?family=Montserrat:light,regular,semibold,bold%7cAbril+Fatface:light,regular,bold
119 ms140 ms1 KB8 KB200text/cssStylesheet
https://api.segment.io/v1/p
219 ms322 ms0 KB0 KB200application/jsonXHR
https://fonts.gstatic.com/s/abrilfatface/v11/zOL64pLDlL1D99S8g8PtiKchq-dmjQ.woff2
238 ms246 ms13 KB13 KB200font/woff2Font
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459Wlhyw.woff2
239 ms244 ms19 KB19 KB200font/woff2Font
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_bZF3gnD_g.woff2
241 ms246 ms19 KB19 KB200font/woff2Font
https://api.segment.io/v1/i
300 ms388 ms0 KB0 KB200application/jsonXHR
https://api.segment.io/v1/p
355 ms697 ms0 KB0 KB200application/jsonXHR
Serve static assets with an efficient cache policy - 3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://cdn.segment.com/analytics.js/v1/v71cnjWvtktQ0qEKxfwPSRyzGsTBuiIa/analytics.min.js
300000 ms56 KB
https://zelas.com.br/static/js/bundle.483d9fc0.js
604800000 ms91 KB
https://zelas.com.br/static/media/zelas-home.cbe466e0.svg
604800000 ms17 KB
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://fonts.gstatic.com/s/abrilfatface/v11/zOL64pLDlL1D99S8g8PtiKchq-dmjQ.woff2
8 ms
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459Wlhyw.woff2
4 ms
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_bZF3gnD_g.woff2
5 ms
Avoids enormous network payloads - Total size was 222 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://zelas.com.br/static/js/bundle.483d9fc0.js
91 KB
https://cdn.segment.com/analytics.js/v1/v71cnjWvtktQ0qEKxfwPSRyzGsTBuiIa/analytics.min.js
56 KB
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_bZF3gnD_g.woff2
19 KB
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459Wlhyw.woff2
19 KB
https://zelas.com.br/static/media/zelas-home.cbe466e0.svg
17 KB
https://fonts.gstatic.com/s/abrilfatface/v11/zOL64pLDlL1D99S8g8PtiKchq-dmjQ.woff2
13 KB
https://zelas.com.br/
3 KB
https://fonts.googleapis.com/css?family=Montserrat:light,regular,semibold,bold%7cAbril+Fatface:light,regular,bold
1 KB
http://zelas.com.br/
0 KB
https://api.segment.io/v1/i
0 KB
Avoids an excessive DOM size - 23 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). Learn more.

Statistic
ElementValue
Total DOM Elements
23
Maximum DOM Depth
8
Maximum Child Elements
6
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://zelas.com.br/)
0
https://zelas.com.br/
190
Keep request counts low and transfer sizes small - 12 requests • 222 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
12222 KB
Script
2148 KB
Font
352 KB
Image
117 KB
Document
13 KB
Stylesheet
11 KB
Other
41 KB
Media
00 KB
Third-party
8110 KB
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

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. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

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. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
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. Learn more.

Serve images in next-gen formats
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. Learn more.

Avoid chaining critical requests - 4 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
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. Learn more.

Server response times are low (TTFB) - Root document took 20 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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


Page Speed (Google PageSpeed Insights) - Mobile

92
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Max Potential First Input Delay 380 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 3.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 100 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. Learn more.
Total Blocking Time 610 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 2160 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 3.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Serve static assets with an efficient cache policy - 3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://cdn.segment.com/analytics.js/v1/v71cnjWvtktQ0qEKxfwPSRyzGsTBuiIa/analytics.min.js
300000 ms56 KB
https://zelas.com.br/static/js/bundle.483d9fc0.js
604800000 ms91 KB
https://zelas.com.br/static/media/zelas-home.cbe466e0.svg
604800000 ms17 KB
Minimize third-party usage - Third-party code blocked the main thread for 240 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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
57 KB240 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
2329 ms
9 ms
2340 ms
5 ms
2345 ms
26 ms
2396 ms
84 ms
2481 ms
16 ms
2498 ms
10 ms
2519 ms
6 ms
2526 ms
94 ms
2632 ms
9 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://fonts.gstatic.com/s/abrilfatface/v11/zOL64pLDlL1D99S8g8PtiKchq-dmjcDidBc.woff2
6 ms
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
6 ms
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_bZF3gnD_vx3rCs.woff2
8 ms
JavaScript execution time - 0.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
445 ms21 ms6 ms
https://zelas.com.br/static/js/bundle.483d9fc0.js
423 ms399 ms23 ms
https://cdn.segment.com/analytics.js/v1/v71cnjWvtktQ0qEKxfwPSRyzGsTBuiIa/analytics.min.js
339 ms300 ms37 ms
Avoids enormous network payloads - Total size was 211 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://zelas.com.br/static/js/bundle.483d9fc0.js
91 KB
https://cdn.segment.com/analytics.js/v1/v71cnjWvtktQ0qEKxfwPSRyzGsTBuiIa/analytics.min.js
56 KB
https://zelas.com.br/static/media/zelas-home.cbe466e0.svg
17 KB
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
14 KB
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_bZF3gnD_vx3rCs.woff2
14 KB
https://fonts.gstatic.com/s/abrilfatface/v11/zOL64pLDlL1D99S8g8PtiKchq-dmjcDidBc.woff2
13 KB
https://zelas.com.br/
3 KB
https://fonts.googleapis.com/css?family=Montserrat:light,regular,semibold,bold%7cAbril+Fatface:light,regular,bold
1 KB
http://zelas.com.br/
0 KB
https://api.segment.io/v1/i
0 KB
Minimizes main-thread work - 1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
738 ms
Other
188 ms
Style & Layout
179 ms
Script Parsing & Compilation
70 ms
Rendering
37 ms
Parse HTML & CSS
16 ms
Avoids an excessive DOM size - 23 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). Learn more.

Statistic
ElementValue
Total DOM Elements
23
Maximum DOM Depth
8
Maximum Child Elements
6
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://zelas.com.br/)
0
https://zelas.com.br/
630
Keep request counts low and transfer sizes small - 12 requests • 211 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
12211 KB
Script
2148 KB
Font
341 KB
Image
117 KB
Document
13 KB
Stylesheet
11 KB
Other
41 KB
Media
00 KB
Third-party
899 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://zelas.com.br/
0 ms88 ms0 KB0 KB301text/html
https://zelas.com.br/
88 ms2298 ms3 KB6 KB200text/htmlDocument
https://zelas.com.br/static/media/zelas-home.cbe466e0.svg
2312 ms2396 ms17 KB22 KB200image/svg+xmlImage
https://zelas.com.br/static/js/bundle.483d9fc0.js
2312 ms2405 ms91 KB282 KB200application/javascriptScript
https://cdn.segment.com/analytics.js/v1/v71cnjWvtktQ0qEKxfwPSRyzGsTBuiIa/analytics.min.js
2315 ms2346 ms56 KB286 KB200text/javascriptScript
https://fonts.googleapis.com/css?family=Montserrat:light,regular,semibold,bold%7cAbril+Fatface:light,regular,bold
2353 ms2376 ms1 KB8 KB200text/cssStylesheet
https://api.segment.io/v1/p
2450 ms2537 ms0 KB0 KB200application/jsonXHR
https://fonts.gstatic.com/s/abrilfatface/v11/zOL64pLDlL1D99S8g8PtiKchq-dmjcDidBc.woff2
2457 ms2463 ms13 KB13 KB200font/woff2Font
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
2459 ms2465 ms14 KB13 KB200font/woff2Font
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_bZF3gnD_vx3rCs.woff2
2462 ms2470 ms14 KB13 KB200font/woff2Font
https://api.segment.io/v1/i
2558 ms2644 ms0 KB0 KB200application/jsonXHR
https://api.segment.io/v1/p
2611 ms2699 ms0 KB0 KB200application/jsonXHR
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. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

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. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
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. Learn more.

Serve images in next-gen formats
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. Learn more.

Avoid chaining critical requests - 4 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
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. Learn more.

Reduce server response times (TTFB) - Root document took 2,210 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://api.segment.io/v1/i (expiration not specified)
https://api.segment.io/v1/p (expiration not specified)
https://cdn.segment.com/***ytics.js/v1/v71cnjWvtktQ0qEKxfwPSRyzGsTBuiIa/***ytics.min.js (5 minutes)
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does zelas.com.br use compression?

zelas.com.br use gzip compression.
Original size: 6.34 KB
Compressed size: 2.83 KB
File reduced by: 3.51 KB (55%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

zelas.com.br supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: zelas.com.br
Organization:
Location:
Issuer: Amazon
Valid from: Jun 6 00:00:00 2019 GMT
Valid until: Jul 6 12:00:00 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

zelas.com.br supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: CloudFront
Date: Sat, 23 Nov 2019 19:31:03 GMT
Content-Type: text/html
Content-Length: 183
Connection: close
Location: https://zelas.com.br/
X-Cache: Redirect from cloudfront
Via: 1.1 7b891ba5ffaf08dd209adf67026190db.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: ORD52-C1
X-Amz-Cf-Id: --bZ70d4cKNqnYgIBhtTjMJVDBCgNGKLj4tlawMz8qnX-Khqhv4aNQ==

HTTP/2 200 
content-type: text/html; charset=utf-8
server: nginx/1.15.9
content-encoding: gzip
date: Sat, 23 Nov 2019 19:31:04 GMT
cache-control: public, max-age=86400
etag: W/"1960-ZMwgL79XVHVkAVPqyWNpQvOWbuU"
vary: Accept-Encoding
x-cache: RefreshHit from cloudfront
via: 1.1 7b891ba5ffaf08dd209adf67026190db.cloudfront.net (CloudFront)
x-amz-cf-pop: ORD52-C1
x-amz-cf-id: Pv2EqGUyebyLFuIVE4QCvHrak57I3-HJdW_mc04gnKsNwkT7bPyX3A==

+ DNS Lookup

Currently Not Available

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.registro.br...
% Copyright (c) Nic.br
% The use of the data below is only permitted as described in
% full by the terms of use at https://registro.br/termo/en.html ,
% being prohibited its distribution, commercialization or
% reproduction, in particular, to use it for advertising or
% any similar purpose.
% 2019-11-23T16:31:22-03:00

domain: zelas.com.br
owner: ESCALE SEO MARKETING DIGITAL LTDA
owner-c: MAKLI6
admin-c: MAKLI6
tech-c: ALGSI491
billing-c: MAKLI6
nserver: ns-1238.awsdns-26.org
nsstat: 20191121 AA
nslastaa: 20191121
nserver: ns-1***6.awsdns-20.co.uk
nsstat: 20191121 AA
nslastaa: 20191121
nserver: ns-460.awsdns-57.com
nsstat: 20191121 AA
nslastaa: 20191121
nserver: ns-553.awsdns-05.net
nsstat: 20191121 AA
nslastaa: 20191121
saci: yes
created: 20190129 #19248100
changed: 20190320
expires: 20200129
status: published

nic-hdl-br: MAKLI6
person: Matt Kligerman
created: 20120831
changed: 20191108

nic-hdl-br: ALGSI491
person: Alex Gomes da Silva
created: 20180822
changed: 20180822

% Security and mail abuse issues should also be addressed to
% cert.br, http://www.cert.br/ , respectivelly to email
% and email
%
% whois.registro.br accepts only direct match queries. Types
% of queries are: domain (.br), registrant (tax ID), ticket,
% provider, contact handle (ID), CIDR block, IP and ASN.
Last update was 131 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with zelas.com.br in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

brestmeat.by
47 secs
belarus.basketball
1 min
bcp.brest.by
2 mins
armenik.com
3 mins
attpasswordhelpsupport.freshdesk.com
3 mins
kap-ko.hr
3 mins
yuksay.com
5 mins
stormark.no
5 mins
taman4dbet.info
5 mins
milliondollarvegan.com
6 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
zelas.com.br widget