Google.Cl - Info google.cl

google.cl receives about 1,377,738 unique visitors and 8,349,090 (6.06 per visitor) page views per day which should earn about $8,920.34/day from advertising revenue. Estimated site value is $6,163,774.42. According to Alexa Traffic Rank google.cl is ranked number 546 in the world and 0.0812% of global Internet users visit it. Site is hosted in Draper, Utah, 84020, United States and links to network IP address 216.58.192.195. This server supports HTTPS and HTTP/2.

About - google.cl

Buscador que enfoca sus resultados para este país y a nivel internacional tanto en español como en inglés.
Edit Site Info

Technologies used on Website

Currently Not Available

google.cl Profile

Title: Google
Description: Buscador que enfoca sus resultados para este país y a nivel internacional tanto en español como en inglés.
Search the world's information, including webpages, images, videos and more. Google has many special features to help you find exactly what you're looking for.
Keywords: google
Last update was 251 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is google.cl?

1.4M daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,377,738
Monthly Unique Visitors:
33,065,712
Pages per Visit:
6.06
Daily Pageviews:
8,349,090
Alexa Rank:
546 visit alexa
Alexa Reach:
0.0812%   (of global internet users)
Avg. visit duration:
11:45
Bounce rate:
37.45%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
60.59%
Referral:
33.76%
Search:
3.40%
Social:
2.23%
Paid:
0.01%

Visitors by country

Users%Pageviews%Rank
Chile 97.4%98.0%4
United States 0.6%0.6%22138

Where do visitors go on this site?

Reach%Pageviews%PerUser
google.cl
95.21%88.23%6.02
translate.google.cl
5.88%10.88%12
books.google.cl
1.44%0.56%2.5
scholar.google.cl
0.94%0.16%1.1
accounts.google.cl
0.72%0.11%1.0
OTHER
0%0.06%0

Competitive Data

SEMrush
Domain:
  google.cl
Rank:
(Rank based on keywords, cost and organic traffic)
  179,552
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  25
Organic Traffic:
(Number of visitors coming from top 20 search results)
  3,555
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1,000.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 google.cl?

Facebook:
  26
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:
google.cl
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:
google.cl
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 google.cl can earn?

Daily Revenue:
$8,920.34
Monthly Revenue:
$267,610.20
Yearly Revenue:
$3,255,924.10
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Chile 8,182,108$8,345.75
United States 50,095$574.58

How much money do google.cl lose due to Adblock?

Daily Revenue Loss:
$1,188.37
Monthly Revenue Loss:
$35,651.18
Yearly Revenue Loss:
$433,756.05
Daily Pageviews Blocked:
1,072,691
Monthly Pageviews Blocked:
32,180,732
Yearly Pageviews Blocked:
391,532,245
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Chile 1,063,674$1,084.95
United States 9,017$103.43

How much is google.cl worth?

Website Value:
$6,163,774.42

+ Where is google.cl hosted?

Server IP:
216.58.192.195
ASN:
AS15169 
ISP:
Google LLC 
Server Location:
Draper
Utah, UT
84020
United States, US
 

Other sites hosted on 216.58.192.195

+ How fast does google.cl load?

Average Load Time:
(1034 ms) 78 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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.

First Contentful Paint (FCP)14.4s 14% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 14% 25% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 25% 59% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 59%
First Input Delay (FID)89ms 90% of loads for this page have a fast (<50ms) First Input Delay (FID) 90% 7% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 7% 2% of loads for this page have a slow (>250ms) First Input Delay (FID) 2%

Origin Data

All pages served from this origin have an SLOW 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.

First Contentful Paint (FCP)4.3s 69% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 69% 14% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 14% 15% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 15%
First Input Delay (FID)90ms 92% of loads for this page have a fast (<50ms) First Input Delay (FID) 92% 5% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 5% 2% of loads for this page have a slow (>250ms) First Input Delay (FID) 2%

Lab Data

First Contentful Paint 0.8 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 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 120 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 1.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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.
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 447 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google.cl/xjs/_/js/k=xjs.s.en_US.pCG8zTK8Tc4.O/ck=xjs.s.4pybrAQhEVc.L.W.O/m=Fkg7bd,HcFEGb,IvlUe,MC8mtf,OF7gzc,RMhBfe,T4BAC,TJw5qb,TbaHGc,Y33vzc,cdos,hsm,iDPoPb,jsa,mvYTse,tg8oTe,uz938c,vWNDde,ws9Tlc,yQ43ff,d,csi/am=AgAAWATYBwgE-f8KAADgEwAABLgLNlggDoSKYXUgAgQ/d=1/dg=2/br=1/ct=zgms/rs=ACT90oGw2kMQP4kOoUSOC8EuMpTxTOuTkA
139 KB
https://www.google.cl/?gws_rd=ssl
65 KB
https://www.gstatic.com/og/_/js/k=og.og2.en_US.GdU2tvYwRSE.O/rt=j/m=def,aswid/exm=in,fot/d=1/ed=1/rs=AA2YrTvGmug-unAddkGu09wbESqi62SHzg
59 KB
https://apis.google.com/_/scs/abc-static/_/js/k=gapi.gapi.en.4CFxRrSvxq0.O/m=gapi_iframes,googleapis_client,plusone/rt=j/sv=1/d=1/ed=1/rs=AHpOoo8skdVJHB5uqGRXCunlhzuKwaF7Ag/cb=gapi.loaded_0
50 KB
https://www.google.cl/xjs/_/js/k=xjs.s.en_US.pCG8zTK8Tc4.O/ck=xjs.s.4pybrAQhEVc.L.W.O/am=AgAAWATYBwgE-f8KAADgEwAABLgLNlggDoSKYXUgAgQ/d=1/exm=Fkg7bd,HcFEGb,IvlUe,MC8mtf,OF7gzc,RMhBfe,T4BAC,TJw5qb,TbaHGc,Y33vzc,cdos,csi,d,hsm,iDPoPb,jsa,mvYTse,tg8oTe,uz938c,vWNDde,ws9Tlc,yQ43ff/ed=1/dg=2/br=1/ct=zgms/rs=ACT90oGw2kMQP4kOoUSOC8EuMpTxTOuTkA/m=aa,abd,async,dvl,fEVMic,foot,ifl,lu,m,mUpTid,mu,sb_wiz,sf,sonic,spch,wft,xz7cCd?xjs=s1
41 KB
https://www.google.cl/logos/doodles/2019/googles-21st-birthday-6038069261107200.2-l.png
31 KB
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
16 KB
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxK.woff2
15 KB
https://ogs.google.com/widget/app/so?hl=en&origin=https%3A%2F%2Fwww.google.cl&pid=1&spid=1&usegapi=1
14 KB
https://ssl.gstatic.com/gb/images/i1_1967ca6a.png
8 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
272 ms
Other
59 ms
Script Parsing & Compilation
54 ms
Style & Layout
30 ms
Parse HTML & CSS
14 ms
Rendering
9 ms
Avoids an excessive DOM size - 218 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
218
Maximum DOM Depth
13
Maximum Child Elements
17
Avoid multiple page redirects - Potential savings of 380 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://google.cl/)
0
http://www.google.cl/
190
https://www.google.cl/?gws_rd=ssl
190
User Timing marks and measures - 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Name
TypeStart TimeDuration
kDcP9b
Measure747 ms1 ms
kDcP9b
Measure777 ms3 ms
O7jPNb
Mark747 ms0 ms
O7jPNb
Mark777 ms0 ms
Keep request counts low and transfer sizes small - 20 requests • 447 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
20447 KB
Script
4290 KB
Document
165 KB
Image
746 KB
Font
231 KB
Other
615 KB
Stylesheet
00 KB
Media
00 KB
Third-party
8163 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://google.cl/
0 ms100 ms0 KB0 KB301text/html
http://www.google.cl/
100 ms189 ms1 KB0 KB302text/html
https://www.google.cl/?gws_rd=ssl
189 ms317 ms65 KB220 KB200text/htmlDocument
https://www.google.cl/logos/doodles/2019/googles-21st-birthday-6038069261107200.2-l.png
344 ms356 ms31 KB31 KB200image/pngImage
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxK.woff2
355 ms359 ms15 KB15 KB200font/woff2Font
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
357 ms361 ms16 KB15 KB200font/woff2Font
https://ssl.gstatic.com/gb/images/i1_1967ca6a.png
366 ms370 ms8 KB7 KB200image/pngImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABYAAAAWCAYAAADEtGw7AAAAoklEQVR42mNIm/mfgQzsAMQzgfgBFM
386 ms386 ms0 KB0 KB200image/pngImage
https://www.gstatic.com/images/branding/googlemic/2x/googlemic_color_24dp.png
396 ms404 ms1 KB1 KB200image/pngImage
https://www.google.cl/images/searchbox/desktop_searchbox_sprites302_hr.webp
396 ms405 ms1 KB1 KB200image/webpImage
https://www.google.cl/gen_204?s=webhp&t=aft&atyp=csi&ei=ptiNXcfxGPG2ggfB3rjoDQ&rt=wsrt.319,aft.91,prt.120&bl=xGob&ima=2&imad=0&imn=2
441 ms452 ms0 KB0 KB-1Other
https://www.google.cl/images/nav_logo299.webp
450 ms456 ms5 KB4 KB200image/webpImage
https://www.google.cl/xjs/_/js/k=xjs.s.en_US.pCG8zTK8Tc4.O/ck=xjs.s.4pybrAQhEVc.L.W.O/m=Fkg7bd,HcFEGb,IvlUe,MC8mtf,OF7gzc,RMhBfe,T4BAC,TJw5qb,TbaHGc,Y33vzc,cdos,hsm,iDPoPb,jsa,mvYTse,tg8oTe,uz938c,vWNDde,ws9Tlc,yQ43ff,d,csi/am=AgAAWATYBwgE-f8KAADgEwAABLgLNlggDoSKYXUgAgQ/d=1/dg=2/br=1/ct=zgms/rs=ACT90oGw2kMQP4kOoUSOC8EuMpTxTOuTkA
454 ms604 ms139 KB442 KB200text/javascriptScript
https://www.gstatic.com/og/_/js/k=og.og2.en_US.GdU2tvYwRSE.O/rt=j/m=def,aswid/exm=in,fot/d=1/ed=1/rs=AA2YrTvGmug-unAddkGu09wbESqi62SHzg
649 ms661 ms59 KB168 KB200text/javascriptScript
https://www.google.cl/gen_204?atyp=csi&ei=ptiNXcfxGPG2ggfB3rjoDQ&s=jsa&jsi=s,t.0,et.focus,n.iDPoPb,cn.1&zx=1569577126948
743 ms792 ms0 KB0 KB-1Other
https://www.google.cl/xjs/_/js/k=xjs.s.en_US.pCG8zTK8Tc4.O/ck=xjs.s.4pybrAQhEVc.L.W.O/am=AgAAWATYBwgE-f8KAADgEwAABLgLNlggDoSKYXUgAgQ/d=1/exm=Fkg7bd,HcFEGb,IvlUe,MC8mtf,OF7gzc,RMhBfe,T4BAC,TJw5qb,TbaHGc,Y33vzc,cdos,csi,d,hsm,iDPoPb,jsa,mvYTse,tg8oTe,uz938c,vWNDde,ws9Tlc,yQ43ff/ed=1/dg=2/br=1/ct=zgms/rs=ACT90oGw2kMQP4kOoUSOC8EuMpTxTOuTkA/m=aa,abd,async,dvl,fEVMic,foot,ifl,lu,m,mUpTid,mu,sb_wiz,sf,sonic,spch,wft,xz7cCd?xjs=s1
785 ms808 ms41 KB129 KB200text/javascriptScript
https://apis.google.com/_/scs/abc-static/_/js/k=gapi.gapi.en.4CFxRrSvxq0.O/m=gapi_iframes,googleapis_client,plusone/rt=j/sv=1/d=1/ed=1/rs=AHpOoo8skdVJHB5uqGRXCunlhzuKwaF7Ag/cb=gapi.loaded_0
828 ms837 ms50 KB144 KB200text/javascriptScript
https://ogs.google.com/widget/app/so?hl=en&origin=https%3A%2F%2Fwww.google.cl&pid=1&spid=1&usegapi=1
854 ms988 ms14 KB0 KB200text/htmlOther
https://www.google.cl/gen_204?atyp=csi&ei=ptiNXcfxGPG2ggfB3rjoDQ&s=webhp&t=all&bl=xGob&imn=2&adh=&conn=onchange&ima=2&imad=0&ime=2&imeb=0&imeo=0&wh=940&scp=0&net=dl.10000,ect.4g,rtt.0&mem=ujhs.22,tjhs.47,jhsl.2330,dm.8&sto=&sys=hc.112&rt=aft.91,iml.91,prt.120,dcl.124,xjsls.135,xjses.358,xjsee.412,xjs.412,ol.635,wsrt.319,cst.0,dnst.0,rqst.129,rspt.0,rqstt.190,unt.190,cstt.190,dit.443&zx=1569577127161
956 ms962 ms0 KB0 KB-1Other
https://adservice.google.cl/adsid/google/ui
959 ms971 ms1 KB0 KB204text/htmlImage
Third-Party Usage - 2 Third-Parties Found
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 Time
60 KB50 ms
50 KB33 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
344 ms
7 ms
353 ms
13 ms
368 ms
13 ms
387 ms
15 ms
416 ms
10 ms
438 ms
36 ms
677 ms
116 ms
795 ms
20 ms
830 ms
51 ms
898 ms
35 ms
933 ms
37 ms
974 ms
11 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/roboto/v18/KFOmCnqEu92Fr1Mu4mxK.woff2
4 ms
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
4 ms
JavaScript execution time - 0.2 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
129 ms21 ms1 ms
https://www.google.cl/xjs/_/js/k=xjs.s.en_US.pCG8zTK8Tc4.O/ck=xjs.s.4pybrAQhEVc.L.W.O/m=Fkg7bd,HcFEGb,IvlUe,MC8mtf,OF7gzc,RMhBfe,T4BAC,TJw5qb,TbaHGc,Y33vzc,cdos,hsm,iDPoPb,jsa,mvYTse,tg8oTe,uz938c,vWNDde,ws9Tlc,yQ43ff,d,csi/am=AgAAWATYBwgE-f8KAADgEwAABLgLNlggDoSKYXUgAgQ/d=1/dg=2/br=1/ct=zgms/rs=ACT90oGw2kMQP4kOoUSOC8EuMpTxTOuTkA
124 ms108 ms17 ms
https://www.google.cl/?gws_rd=ssl
66 ms48 ms16 ms
Remove unused CSS - Potential savings of 17 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. Learn more.

URL
SizePotential Savings
@-webkit-keyframes gb__a{0%{opacity:0} ...
12 KB11 KB
@-webkit-keyframes gb__a{0%{opacity:0} ...
3 KB3 KB
.y,.yp,.yf,.yi,.yl,.ye{} ...
3 KB3 KB
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.

Minimize Critical Requests Depth - 2 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.

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 130 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.

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

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

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. 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.

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.


Page Speed (Google PageSpeed Insights) - Mobile

89
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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.

First Contentful Paint (FCP)2.2s 14% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 67% 24% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 24% 8% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 8%
First Input Delay (FID)320ms 76% of loads for this page have a fast (<50ms) First Input Delay (FID) 76% 16% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 16% 7% of loads for this page have a slow (>250ms) First Input Delay (FID) 7%

Origin Data

All pages served from this origin have an SLOW 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.

First Contentful Paint (FCP)1.4s 83% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 83% 12% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 12% 3% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 3%
First Input Delay (FID)251ms 92% of loads for this page have a fast (<50ms) First Input Delay (FID) 82% 12% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 12% 5% of loads for this page have a slow (>250ms) First Input Delay (FID) 5%

Lab Data

First Contentful Paint 1.9 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 2.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 460 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 4.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 130 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.
First Contentful Paint (3G) 3990 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 640 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 4.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 318 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google.cl/xjs/_/js/k=xjs.qs.en_US.ef81iY4DgUo.O/ck=xjs.qs.YKMqfGtuA_0.L.W.O/m=ByqdBd,CiVnBc,Fkg7bd,HcFEGb,OF7gzc,QfiAub,RMhBfe,T4BAC,Uox2uf,bct,cdos,czrJpf,hsm,if1iFc,jsa,kopZwe,lXXCK,qim,uz938c,vWNDde,ws9Tlc,xPR7tc,yQ43ff,d,csi/am=AAAAgEUo_8xMOYQYAIg-AQBQBKfB_gXAcAIgQrQSBw/d=1/dg=2/br=1/ct=zgms/rs=ACT90oGhfnj1Beaykj9uU7qWWIOm9_5MLg
163 KB
https://www.google.cl/?gws_rd=ssl
42 KB
https://www.google.cl/xjs/_/js/k=xjs.qs.en_US.ef81iY4DgUo.O/ck=xjs.qs.YKMqfGtuA_0.L.W.O/am=AAAAgEUo_8xMOYQYAIg-AQBQBKfB_gXAcAIgQrQSBw/d=1/exm=ByqdBd,CiVnBc,Fkg7bd,HcFEGb,OF7gzc,QfiAub,RMhBfe,T4BAC,Uox2uf,bct,cdos,csi,czrJpf,d,hsm,if1iFc,jsa,kopZwe,lXXCK,qim,uz938c,vWNDde,ws9Tlc,xPR7tc,yQ43ff/ed=1/dg=2/br=1/ct=zgms/rs=ACT90oGhfnj1Beaykj9uU7qWWIOm9_5MLg/m=CHeGN,aa,abd,async,dvl,fEVMic,foot,mUpTid,mu,rQSi2,sb_wiz,sf,sonic,spch,xz7cCd?xjs=s1
41 KB
https://www.google.cl/logos/doodles/2019/googles-21st-birthday-6038069261107200.2-l.png
31 KB
https://www.gstatic.com/og/_/js/k=og.mob.en_US.g_USH5odIW8.O/rt=j/m=md/exm=mih,mab,meb/d=1/ed=1/rs=AA2YrTvJCaOmerkP2m_PPAztfcHpUJBHlQ
20 KB
https://www.google.cl/images/nav_logo289_hr.webp
5 KB
https://ssl.gstatic.com/gb/images/qi2_00ed8ca1.png
4 KB
https://www.gstatic.com/og/_/ss/k=og.mob.28e7vtq8fbip.L.W.O/m=md/excm=mih,mab,meb/d=1/ed=1/rs=AA2YrTuTu1NMRNt8g5lsPtRFD1J0fl0dbg
3 KB
https://www.gstatic.com/navigationdrawer/save_icon.svg
1 KB
https://www.gstatic.com/navigationdrawer/settings_icon.svg
1 KB
Minimizes main-thread work - 1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
1141 ms
Other
262 ms
Style & Layout
146 ms
Script Parsing & Compilation
130 ms
Parse HTML & CSS
52 ms
Rendering
18 ms
Avoids an excessive DOM size - 428 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
428
Maximum DOM Depth
17
Maximum Child Elements
17
Avoid multiple page redirects - Potential savings of 1,260 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://google.cl/)
0
http://www.google.cl/
630
https://www.google.cl/?gws_rd=ssl
630
User Timing marks and measures - 2 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Name
TypeStart TimeDuration
kDcP9b
Measure658 ms34 ms
O7jPNb
Mark658 ms0 ms
Keep request counts low and transfer sizes small - 24 requests • 318 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
24318 KB
Script
3224 KB
Image
1548 KB
Document
142 KB
Stylesheet
13 KB
Other
41 KB
Media
00 KB
Font
00 KB
Third-party
1334 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://google.cl/
0 ms94 ms0 KB0 KB301text/html
http://www.google.cl/
95 ms230 ms1 KB0 KB302text/html
https://www.google.cl/?gws_rd=ssl
231 ms363 ms42 KB135 KB200text/htmlDocument
https://www.google.cl/logos/doodles/2019/googles-21st-birthday-6038069261107200.2-l.png
377 ms386 ms31 KB31 KB200image/pngImage
https://ssl.gstatic.com/gb/images/qi2_00ed8ca1.png
392 ms396 ms4 KB3 KB200image/pngImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABYAAAAWCAYAAADEtGw7AAAAoklEQVR42mNIm/mfgQzsAMQzgfgBFM
412 ms412 ms0 KB0 KB200image/pngImage
https://www.gstatic.com/og/_/js/k=og.mob.en_US.g_USH5odIW8.O/rt=j/m=md/exm=mih,mab,meb/d=1/ed=1/rs=AA2YrTvJCaOmerkP2m_PPAztfcHpUJBHlQ
457 ms463 ms20 KB56 KB200text/javascriptScript
https://www.google.cl/gen_204?s=webhp&t=aft&atyp=csi&ei=oNiNXfS7Ksmc_Qah0p6oBg&rt=wsrt.364,aft.96,prt.102&bl=xGob&ima=2&imad=0&imn=2
467 ms472 ms0 KB0 KB-1Other
https://www.google.cl/images/nav_logo289_hr.webp
470 ms477 ms5 KB5 KB200image/webpImage
https://www.google.cl/xjs/_/js/k=xjs.qs.en_US.ef81iY4DgUo.O/ck=xjs.qs.YKMqfGtuA_0.L.W.O/m=ByqdBd,CiVnBc,Fkg7bd,HcFEGb,OF7gzc,QfiAub,RMhBfe,T4BAC,Uox2uf,bct,cdos,czrJpf,hsm,if1iFc,jsa,kopZwe,lXXCK,qim,uz938c,vWNDde,ws9Tlc,xPR7tc,yQ43ff,d,csi/am=AAAAgEUo_8xMOYQYAIg-AQBQBKfB_gXAcAIgQrQSBw/d=1/dg=2/br=1/ct=zgms/rs=ACT90oGhfnj1Beaykj9uU7qWWIOm9_5MLg
473 ms493 ms163 KB520 KB200text/javascriptScript
https://www.google.cl/xjs/_/js/k=xjs.qs.en_US.ef81iY4DgUo.O/ck=xjs.qs.YKMqfGtuA_0.L.W.O/am=AAAAgEUo_8xMOYQYAIg-AQBQBKfB_gXAcAIgQrQSBw/d=1/exm=ByqdBd,CiVnBc,Fkg7bd,HcFEGb,OF7gzc,QfiAub,RMhBfe,T4BAC,Uox2uf,bct,cdos,csi,czrJpf,d,hsm,if1iFc,jsa,kopZwe,lXXCK,qim,uz938c,vWNDde,ws9Tlc,xPR7tc,yQ43ff/ed=1/dg=2/br=1/ct=zgms/rs=ACT90oGhfnj1Beaykj9uU7qWWIOm9_5MLg/m=CHeGN,aa,abd,async,dvl,fEVMic,foot,mUpTid,mu,rQSi2,sb_wiz,sf,sonic,spch,xz7cCd?xjs=s1
701 ms711 ms41 KB130 KB200text/javascriptScript
https://www.gstatic.com/navigationdrawer/home_icon.svg
718 ms723 ms1 KB0 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/search_activity_icon.svg
718 ms723 ms1 KB0 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/save_icon.svg
719 ms727 ms1 KB1 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/manage_searches_icon.png
719 ms723 ms1 KB0 KB200image/pngImage
https://www.gstatic.com/navigationdrawer/settings_icon.svg
719 ms724 ms1 KB1 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/privacy_advisor_icon.svg
720 ms724 ms1 KB1 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/how_search_works_icon.svg
720 ms726 ms1 KB0 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/help_icon.svg
720 ms726 ms1 KB0 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/feedback_icon.svg
721 ms726 ms1 KB0 KB200image/svg+xmlImage
https://www.google.cl/gen_204?atyp=i&ct=mhp_asic&cad=&vet=10ahUKEwj0i-i12vDkAhVJTt8KHSGpB2UQ1MADCA8..s&ei=oNiNXfS7Ksmc_Qah0p6oBg&zx=1569577121140
721 ms798 ms0 KB0 KB204text/htmlImage
https://www.gstatic.com/og/_/ss/k=og.mob.28e7vtq8fbip.L.W.O/m=md/excm=mih,mab,meb/d=1/ed=1/rs=AA2YrTuTu1NMRNt8g5lsPtRFD1J0fl0dbg
829 ms835 ms3 KB15 KB200text/cssStylesheet
https://www.google.cl/gen_204?atyp=csi&ei=oNiNXfS7Ksmc_Qah0p6oBg&s=webhp&t=all&bl=xGob&imn=2&adh=&conn=onchange&ima=2&imad=0&ime=2&imeb=0&imeo=0&wh=660&scp=0&net=dl.9100,ect.4g,rtt.0&mem=ujhs.28,tjhs.45,jhsl.2330,dm.8&sto=&sys=hc.48&rt=aft.96,iml.96,prt.102,dcl.106,xjsls.109,xjses.194,xjsee.285,xjs.285,ol.465,wsrt.364,cst.0,dnst.0,rqst.133,rspt.0,rqstt.231,unt.231,cstt.231,dit.469&zx=1569577121268
837 ms860 ms0 KB0 KB-1Other
https://adservice.google.cl/adsid/google/ui
854 ms884 ms1 KB0 KB204text/htmlImage
Third-Party Usage - 1 Third-Party Found
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 Time
30 KB72 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
388 ms
8 ms
398 ms
9 ms
411 ms
14 ms
428 ms
6 ms
436 ms
19 ms
460 ms
20 ms
483 ms
9 ms
501 ms
5 ms
558 ms
115 ms
674 ms
81 ms
801 ms
40 ms
846 ms
32 ms
JavaScript execution time - 1.3 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
681 ms204 ms4 ms
https://www.google.cl/xjs/_/js/k=xjs.qs.en_US.ef81iY4DgUo.O/ck=xjs.qs.YKMqfGtuA_0.L.W.O/m=ByqdBd,CiVnBc,Fkg7bd,HcFEGb,OF7gzc,QfiAub,RMhBfe,T4BAC,Uox2uf,bct,cdos,czrJpf,hsm,if1iFc,jsa,kopZwe,lXXCK,qim,uz938c,vWNDde,ws9Tlc,xPR7tc,yQ43ff,d,csi/am=AAAAgEUo_8xMOYQYAIg-AQBQBKfB_gXAcAIgQrQSBw/d=1/dg=2/br=1/ct=zgms/rs=ACT90oGhfnj1Beaykj9uU7qWWIOm9_5MLg
628 ms567 ms61 ms
https://www.google.cl/?gws_rd=ssl
209 ms169 ms39 ms
https://www.google.cl/xjs/_/js/k=xjs.qs.en_US.ef81iY4DgUo.O/ck=xjs.qs.YKMqfGtuA_0.L.W.O/am=AAAAgEUo_8xMOYQYAIg-AQBQBKfB_gXAcAIgQrQSBw/d=1/exm=ByqdBd,CiVnBc,Fkg7bd,HcFEGb,OF7gzc,QfiAub,RMhBfe,T4BAC,Uox2uf,bct,cdos,csi,czrJpf,d,hsm,if1iFc,jsa,kopZwe,lXXCK,qim,uz938c,vWNDde,ws9Tlc,xPR7tc,yQ43ff/ed=1/dg=2/br=1/ct=zgms/rs=ACT90oGhfnj1Beaykj9uU7qWWIOm9_5MLg/m=CHeGN,aa,abd,async,dvl,fEVMic,foot,mUpTid,mu,rQSi2,sb_wiz,sf,sonic,spch,xz7cCd?xjs=s1
157 ms138 ms19 ms
https://www.gstatic.com/og/_/js/k=og.mob.en_US.g_USH5odIW8.O/rt=j/m=md/exm=mih,mab,meb/d=1/ed=1/rs=AA2YrTvJCaOmerkP2m_PPAztfcHpUJBHlQ
72 ms64 ms7 ms
Defer offscreen images - Potential savings of 5 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

URL
SizePotential Savings
https://www.google.cl/images/nav_logo289_hr.webp
5 KB5 KB
Remove unused CSS - Potential savings of 3 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. Learn more.

URL
SizePotential Savings
https://www.gstatic.com/og/_/ss/k=og.mob.28e7vtq8fbip.L.W.O/m=md/excm=mih,mab,meb/d=1/ed=1/rs=AA2YrTuTu1NMRNt8g5lsPtRFD1J0fl0dbg
3 KB3 KB
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.

Minimize Critical Requests Depth - 1 chain 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.

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 130 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.

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

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

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. 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.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 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.

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

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://google.cl/
http://www.google.cl/
https://www.google.cl/?gws_rd=ssl
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.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
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 google.cl use compression?

google.cl use gzip compression.
Original size: 46.83 KB
Compressed size: 15.58 KB
File reduced by: 31.25 KB (66%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  93
Vendor reliability:
  93
Privacy:
  93
Child safety:
  91

+ SSL Checker - SSL Certificate Verify

google.cl supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: google.com
Organization: Google LLC
Location: Mountain View, California, US
Issuer: GTS CA 1O1
Valid from: Sep 5 20:19:46 2019 GMT
Valid until: Nov 28 20:19:46 2019 GMT
Authority: Is not a CA
Keysize:
Common Name: GTS CA 1O1
Organization: Google Trust Services
Location: US
Issuer: GlobalSign
Valid from: Jun 15 00:00:42 2017 GMT
Valid until: Dec 15 00:00:42 2021 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

google.cl supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Chile/Guías y directorios

+ Http Header

Location: http://www.google.cl/
Content-Type: text/html; charset=UTF-8
Date: Fri, 27 Sep 2019 09:38:25 GMT
Expires: Sun, 27 Oct 2019 09:38:25 GMT
Cache-Control: public, max-age=2592000
Server: gws
Content-Length: 218
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN

HTTP/1.1 200 OK
Date: Fri, 27 Sep 2019 09:38:25 GMT
Expires: -1
Cache-Control: private, max-age=0
Content-Type: text/html; charset=UTF-8
P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
Content-Encoding: gzip
Server: gws
Content-Length: 15949
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Set-Cookie: 1P_JAR=2019-09-27-09; expires=Sun, 27-Oct-2019 09:38:25 GMT; path=/; domain=.google.cl; SameSite=none
Set-Cookie: NID=188=S6A-fnDFgiMxL1TF9hjqflBAAhZ-NUsB4MiJslxJljMTrMBUct59BIPiBry7gIvQPTmS8Nl570pAihLfFVi82xqh_7kITREo3Ls84KX0t6zKjae64TI97XMp10AqakmDf0thEFrzrMWQ0_h1LbojyIZs8U_e1Af2vmgQT_5Ihbo; expires=Sat, 28-Mar-2020 09:38:25 GMT; path=/; domain=.google.cl; HttpOnly

+ DNS Lookup

Currently Not Available

+ Whois Lookup

Domain Created:
2002-10-22
Domain Age:
16 years 11 months 5 days  
WhoIs:
 

whois lookup at whois.nic.cl...
%%
%% This is the NIC Chile Whois server (whois.nic.cl).
%%
%% Rights restricted by copyright.
%% See https://www.nic.cl/normativa/politica-publicacion-de-datos-cl.pdf
%%

Domain name: google.cl
Registrant name: Google Inc.
Registrant organisation:
Registrar name: MarkMonitor Inc.
Registrar URL: https://markmonitor.com/
Creation date: 2002-10-22 17:48:23 CLST
Expiration date: 2019-11-20 14:48:02 CLST
Name server: ns1.google.com
Name server: ns2.google.com
Name server: ns3.google.com
Name server: ns4.google.com

%%
%% For communication with domain contacts please use website.
%% See https://www.nic.cl/registry/Whois.do?d=google.cl
%%
Last update was 251 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with google.cl in any way. Only publicly available statistics data are displayed.
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!
google.cl widget