Google.Pt - Info google.pt

google.pt receives about 2,794,329 unique visitors and 9,416,890 (3.37 per visitor) page views per day which should earn about $20,039.71/day from advertising revenue. Estimated site value is $14,628,991.28. According to Alexa Traffic Rank google.pt is ranked number 829 in the world and 0.0616% of global Internet users visit it. Site is hosted in Draper, Utah, 84020, United States and links to network IP address 172.217.0.3. This server supports HTTPS and HTTP/2.

About - google.pt


Technologies used on Website

Web Servers
Google Web Server

google.pt Profile

Title: Google
Description: 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 27 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is google.pt?

2.8M daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
2,794,329
Monthly Unique Visitors:
67,063,896
Pages per Visit:
3.37
Daily Pageviews:
9,416,890
Alexa Rank:
829 visit alexa
Alexa Reach:
0.0616%   (of global internet users)
Avg. visit duration:
07:50
Bounce rate:
30.92%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
90.46%
Referral:
1.69%
Search:
6.22%
Social:
1.30%
Paid:
0.02%

Visitors by country

Users%Pageviews%Rank
Portugal 81.1%79.8%3
Angola 7.0%3.7%71
Brazil 4.5%3.5%876
Luxembourg 1.8%6.6%18
Japan 1.1%1.9%6074
France 1.0%0.3%3232
Poland 0.6%0.2%2458

Where do visitors go on this site?

Reach%Pageviews%PerUser
google.pt
93.27%95.77%3.4
translate.google.pt
6.19%2.94%1.6
books.google.pt
1.44%0.55%1.3
accounts.google.pt
0.75%0.23%1
scholar.google.pt
0.48%0.19%1
OTHER
0%0.32%0

Competitive Data

SEMrush
Domain:
  google.pt
Rank:
(Rank based on keywords, cost and organic traffic)
  5,477
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  13,591
Organic Traffic:
(Number of visitors coming from top 20 search results)
  304,215
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $752,556.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:
  91
Page Authority:
  59
MozRank:
  6

+ How socially engaged is google.pt?

Facebook:
  14
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.pt
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:12
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.)
Passing


Mobile summary

Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:12
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.)
Passing

+ Abusive Experience Report

Root domain:
google.pt
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:12
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.)
Passing

+ How much google.pt can earn?

Daily Revenue:
$20,039.71
Monthly Revenue:
$601,191.30
Yearly Revenue:
$7,314,494.15
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Portugal 7,514,678$16,382.00
Luxembourg 621,515$1,404.62
Angola 348,425$930.29
Brazil 329,591$583.38
Japan 178,921$572.55
France 28,251$132.78
Poland 18,834$34.09

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

Daily Revenue Loss:
$3,747.55
Monthly Revenue Loss:
$112,426.59
Yearly Revenue Loss:
$1,367,856.87
Daily Pageviews Blocked:
1,712,744
Monthly Pageviews Blocked:
51,382,319
Yearly Pageviews Blocked:
625,151,543
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Portugal 1,578,082$3,440.22
Luxembourg 93,227$210.69
Brazil 19,775$35.00
Angola 6,968$18.61
Japan 5,368$17.18
France 3,108$14.61
Poland 6,215$11.25

How much is google.pt worth?

Website Value:
$14,628,991.28

+ Where is google.pt hosted?

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

Other sites hosted on 172.217.0.3

+ How fast does google.pt load?

Average Load Time:
(1022 ms) 78 % 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 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)10.2s 21% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 21% 29% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 29% 48% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 48%
First Input Delay (FID)75ms 91% of loads for this page have a fast (<50ms) First Input Delay (FID) 91% 6% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 6% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

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)3.3s 70% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 70% 15% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 15% 13% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 13%
First Input Delay (FID)85ms 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 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 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 1.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.1 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 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.

Screenshot Thumbnails

This is what the load of your site looked like.

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.pt/)
0
http://www.google.pt/
190
https://www.google.pt/?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
Measure513 ms1 ms
kDcP9b
Measure533 ms2 ms
O7jPNb
Mark513 ms0 ms
O7jPNb
Mark533 ms0 ms
Keep request counts low and transfer sizes small - 21 requests • 448 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

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

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://google.pt/
0 ms75 ms0 KB0 KB301text/html
http://www.google.pt/
77 ms123 ms1 KB0 KB302text/html
https://www.google.pt/?gws_rd=ssl
124 ms232 ms65 KB220 KB200text/htmlDocument
https://www.google.pt/logos/doodles/2019/googles-21st-birthday-6038069261107200.2-l.png
264 ms270 ms31 KB31 KB200image/pngImage
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxK.woff2
275 ms279 ms15 KB15 KB200font/woff2Font
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
277 ms281 ms16 KB15 KB200font/woff2Font
https://ssl.gstatic.com/gb/images/i1_1967ca6a.png
289 ms293 ms8 KB7 KB200image/pngImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABYAAAAWCAYAAADEtGw7AAAAoklEQVR42mNIm/mfgQzsAMQzgfgBFM
317 ms317 ms0 KB0 KB200image/pngImage
https://www.gstatic.com/images/branding/googlemic/2x/googlemic_color_24dp.png
326 ms333 ms1 KB1 KB200image/pngImage
https://www.google.pt/images/searchbox/desktop_searchbox_sprites302_hr.webp
327 ms347 ms1 KB1 KB200image/webpImage
https://www.google.pt/gen_204?s=webhp&t=aft&atyp=csi&ei=pSOOXaDAMsnI5gKPh6_gBA&rt=wsrt.233,aft.107,prt.137&bl=xGob&ima=2&imad=0&imn=2
373 ms384 ms0 KB0 KB-1Other
https://www.google.pt/images/nav_logo299.webp
381 ms387 ms5 KB4 KB200image/webpImage
https://www.google.pt/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=AgAAWATY7w4E-f8KAADgEwAABLgLNlggDoSKYXUgAgQ/d=1/dg=2/br=1/ct=zgms/rs=ACT90oHS6LhPYerAEjm63tPPNAOA6F0oJw
385 ms402 ms139 KB442 KB200text/javascriptScript
https://www.google.pt/gen_204?atyp=csi&ei=pSOOXaDAMsnI5gKPh6_gBA&s=jsa&jsi=s,t.0,et.focus,n.iDPoPb,cn.1&zx=1569596326204
510 ms541 ms0 KB0 KB-1Other
https://www.google.pt/xjs/_/js/k=xjs.s.en_US.pCG8zTK8Tc4.O/ck=xjs.s.4pybrAQhEVc.L.W.O/am=AgAAWATY7w4E-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=ACT90oHS6LhPYerAEjm63tPPNAOA6F0oJw/m=aa,abd,async,dvl,fEVMic,foot,ifl,lu,m,mUpTid,mu,sb_wiz,sf,sonic,spch,wft,xz7cCd?xjs=s1
539 ms549 ms41 KB129 KB200text/javascriptScript
https://www.google.pt/gen_204?atyp=csi&ei=pSOOXaDAMsnI5gKPh6_gBA&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.23,tjhs.45,jhsl.2330,dm.8&sto=&sys=hc.112&rt=aft.107,iml.107,prt.137,dcl.142,xjsls.152,xjses.227,xjsee.268,xjs.268,ol.360,wsrt.233,cst.0,dnst.0,rqst.109,rspt.0,rqstt.124,unt.124,cstt.124,dit.374&zx=1569596326289
594 ms601 ms0 KB0 KB-1Other
https://adservice.google.pt/adsid/google/ui
596 ms613 ms1 KB0 KB204text/htmlImage
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
600 ms609 ms59 KB168 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
635 ms711 ms50 KB144 KB200text/javascriptScript
https://ogs.google.com/widget/app/so?hl=en&origin=https%3A%2F%2Fwww.google.pt&pid=1&spid=1&usegapi=1
654 ms721 ms14 KB0 KB200text/htmlOther
https://play.google.com/log?format=json&hasfast=true
1384 ms1392 ms1 KB0 KB200text/plainXHR
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 KB35 ms
50 KB26 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
254 ms
10 ms
267 ms
15 ms
285 ms
14 ms
305 ms
22 ms
330 ms
7 ms
343 ms
11 ms
366 ms
34 ms
459 ms
90 ms
550 ms
11 ms
580 ms
28 ms
610 ms
7 ms
641 ms
36 ms
740 ms
28 ms
1397 ms
6 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
128 ms15 ms1 ms
https://www.google.pt/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=AgAAWATY7w4E-f8KAADgEwAABLgLNlggDoSKYXUgAgQ/d=1/dg=2/br=1/ct=zgms/rs=ACT90oHS6LhPYerAEjm63tPPNAOA6F0oJw
94 ms78 ms16 ms
https://www.google.pt/?gws_rd=ssl
72 ms56 ms14 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
Avoids enormous network payloads - Total size was 448 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google.pt/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=AgAAWATY7w4E-f8KAADgEwAABLgLNlggDoSKYXUgAgQ/d=1/dg=2/br=1/ct=zgms/rs=ACT90oHS6LhPYerAEjm63tPPNAOA6F0oJw
139 KB
https://www.google.pt/?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.pt/xjs/_/js/k=xjs.s.en_US.pCG8zTK8Tc4.O/ck=xjs.s.4pybrAQhEVc.L.W.O/am=AgAAWATY7w4E-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=ACT90oHS6LhPYerAEjm63tPPNAOA6F0oJw/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.pt/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.pt&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
222 ms
Other
56 ms
Script Parsing & Compilation
44 ms
Style & Layout
35 ms
Parse HTML & CSS
16 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
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 110 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.

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.

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.

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.


Page Speed (Google PageSpeed Insights) - Mobile

87
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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)1.2s 21% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 68% 26% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 26% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)251ms 85% of loads for this page have a fast (<100ms) First Input Delay (FID) 85% 10% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 10% 3% of loads for this page have a slow (>300ms) First Input Delay (FID) 3%

Origin Data

All pages served from this origin have an AVERAGE 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)700ms 84% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 84% 12% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 12% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)229ms 92% of loads for this page have a fast (<100ms) First Input Delay (FID) 88% 7% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 7% 3% of loads for this page have a slow (>300ms) First Input Delay (FID) 3%

Lab Data

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

Screenshot Thumbnails

This is what the load of your site looked like.

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

URL
Total CPU TimeScript EvaluationScript Parse
Other
598 ms95 ms4 ms
https://www.google.pt/xjs/_/js/k=xjs.qs.en_US.66-oy4Lyz2o.O/ck=xjs.qs.MYEls5vNLNw.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=AAAAACzCyE9mGOWIYgAIZI8BAAATcBbsL4AIngAQIIIaBAU/d=1/dg=2/br=1/ct=zgms/rs=ACT90oG8Paes6HrdAD-YAzX0AQZziVCsNA
422 ms336 ms86 ms
https://www.google.pt/xjs/_/js/k=xjs.qs.en_US.66-oy4Lyz2o.O/ck=xjs.qs.MYEls5vNLNw.L.W.O/am=AAAAACzCyE9mGOWIYgAIZI8BAAATcBbsL4AIngAQIIIaBAU/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=ACT90oG8Paes6HrdAD-YAzX0AQZziVCsNA/m=CHeGN,MkHyGd,NpD4ec,OG6ZHd,RqxLvf,T7XTS,URQPYc,aa,abd,async,dvl,eN4qad,fEVMic,foot,mUpTid,mhp,mu,o02Jie,pB6Zqd,qmp,rHjpXd,rQSi2,sb_wiz,sf,sonic,spch,uiNkee,xz7cCd,zbML3c?xjs=s1
369 ms302 ms28 ms
https://www.google.pt/?gws_rd=ssl
159 ms119 ms39 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.pt/images/nav_logo289_hr.webp
5 KB5 KB
Avoids enormous network payloads - Total size was 332 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google.pt/xjs/_/js/k=xjs.qs.en_US.66-oy4Lyz2o.O/ck=xjs.qs.MYEls5vNLNw.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=AAAAACzCyE9mGOWIYgAIZI8BAAATcBbsL4AIngAQIIIaBAU/d=1/dg=2/br=1/ct=zgms/rs=ACT90oG8Paes6HrdAD-YAzX0AQZziVCsNA
165 KB
https://www.google.pt/xjs/_/js/k=xjs.qs.en_US.66-oy4Lyz2o.O/ck=xjs.qs.MYEls5vNLNw.L.W.O/am=AAAAACzCyE9mGOWIYgAIZI8BAAATcBbsL4AIngAQIIIaBAU/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=ACT90oG8Paes6HrdAD-YAzX0AQZziVCsNA/m=CHeGN,MkHyGd,NpD4ec,OG6ZHd,RqxLvf,T7XTS,URQPYc,aa,abd,async,dvl,eN4qad,fEVMic,foot,mUpTid,mhp,mu,o02Jie,pB6Zqd,qmp,rHjpXd,rQSi2,sb_wiz,sf,sonic,spch,uiNkee,xz7cCd,zbML3c?xjs=s1
66 KB
https://www.google.pt/?gws_rd=ssl
44 KB
https://www.gstatic.com/og/_/js/k=og.mob.en_US.m2VOzIeM7mw.O/rt=j/m=md/exm=mih,mab,meb/d=1/ed=1/rs=AA2YrTv0gYPBFzyzbDfSq1NXJLqsJGLHgw
20 KB
https://www.google.pt/images/branding/googlelogo/2x/googlelogo_color_160x56dp.png
7 KB
https://www.google.pt/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.-1pfbx5fxsfgj4.L.W.O/m=md/excm=mih,mab,meb/d=1/ed=1/ct=zgms/rs=AA2YrTuu5Uuoh9qusE7aQv2bi07p2SR6kA
3 KB
https://www.google.com/images/hpp/googleg-standard-color-104dp.png
3 KB
https://www.google.pt/images/searchbox/searchbox_sprites312_hr.webp
2 KB
Minimizes main-thread work - 1.6 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
890 ms
Other
251 ms
Script Parsing & Compilation
164 ms
Style & Layout
133 ms
Rendering
74 ms
Parse HTML & CSS
46 ms
Garbage Collection
36 ms
Avoids an excessive DOM size - 463 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
463
Maximum DOM Depth
17
Maximum Child Elements
18
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.pt/)
0
http://www.google.pt/
630
https://www.google.pt/?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
Measure771 ms19 ms
O7jPNb
Mark771 ms0 ms
Keep request counts low and transfer sizes small - 29 requests • 332 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
29332 KB
Script
3251 KB
Document
144 KB
Image
1932 KB
Stylesheet
13 KB
Other
51 KB
Media
00 KB
Font
00 KB
Third-party
1339 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://google.pt/
0 ms101 ms0 KB0 KB301text/html
http://www.google.pt/
101 ms175 ms0 KB0 KB302text/html
https://www.google.pt/?gws_rd=ssl
176 ms331 ms44 KB141 KB200text/htmlDocument
https://www.google.com/images/hpp/googleg-standard-color-104dp.png
346 ms363 ms3 KB3 KB200image/pngImage
https://www.google.pt/images/branding/googlelogo/2x/googlelogo_color_160x56dp.png
346 ms373 ms7 KB7 KB200image/pngImage
https://ssl.gstatic.com/gb/images/qi2_00ed8ca1.png
363 ms367 ms4 KB3 KB200image/pngImage
https://www.google.pt/images/searchbox/searchbox_sprites312_hr.webp
389 ms412 ms2 KB1 KB200image/webpImage
https://www.gstatic.com/og/_/js/k=og.mob.en_US.m2VOzIeM7mw.O/rt=j/m=md/exm=mih,mab,meb/d=1/ed=1/rs=AA2YrTv0gYPBFzyzbDfSq1NXJLqsJGLHgw
414 ms420 ms20 KB58 KB200text/javascriptScript
https://www.google.pt/gen_204?s=webhp&t=aft&atyp=csi&ei=vildXrvmJomUtQX-7JOACw&rt=wsrt.332,aft.85,prt.91&bl=UTk5&ima=1&imad=0&imn=2
423 ms428 ms0 KB0 KB-1Other
https://www.google.pt/gen_204?atyp=i&ct=rfl&cad=&ei=vildXrvmJomUtQX-7JOACw&zx=1583163838841
425 ms486 ms0 KB0 KB204text/htmlImage
https://www.google.pt/images/nav_logo289_hr.webp
427 ms436 ms5 KB5 KB200image/webpImage
https://www.google.pt/xjs/_/js/k=xjs.qs.en_US.66-oy4Lyz2o.O/ck=xjs.qs.MYEls5vNLNw.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=AAAAACzCyE9mGOWIYgAIZI8BAAATcBbsL4AIngAQIIIaBAU/d=1/dg=2/br=1/ct=zgms/rs=ACT90oG8Paes6HrdAD-YAzX0AQZziVCsNA
429 ms639 ms165 KB532 KB200text/javascriptScript
https://www.google.pt/xjs/_/js/k=xjs.qs.en_US.66-oy4Lyz2o.O/ck=xjs.qs.MYEls5vNLNw.L.W.O/am=AAAAACzCyE9mGOWIYgAIZI8BAAATcBbsL4AIngAQIIIaBAU/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=ACT90oG8Paes6HrdAD-YAzX0AQZziVCsNA/m=CHeGN,MkHyGd,NpD4ec,OG6ZHd,RqxLvf,T7XTS,URQPYc,aa,abd,async,dvl,eN4qad,fEVMic,foot,mUpTid,mhp,mu,o02Jie,pB6Zqd,qmp,rHjpXd,rQSi2,sb_wiz,sf,sonic,spch,uiNkee,xz7cCd,zbML3c?xjs=s1
795 ms810 ms66 KB211 KB200text/javascriptScript
https://www.gstatic.com/navigationdrawer/home_icon.svg
802 ms814 ms1 KB0 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/search_activity_icon.svg
802 ms813 ms1 KB0 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/save_icon.svg
802 ms813 ms1 KB1 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/manage_searches_icon.png
802 ms815 ms1 KB0 KB200image/pngImage
https://www.gstatic.com/navigationdrawer/settings_icon.svg
803 ms814 ms1 KB1 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/privacy_advisor_icon.svg
803 ms815 ms1 KB1 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/how_search_works_icon.svg
803 ms816 ms1 KB0 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/help_icon.svg
803 ms815 ms1 KB0 KB200image/svg+xmlImage
https://www.gstatic.com/navigationdrawer/feedback_icon.svg
804 ms816 ms1 KB0 KB200image/svg+xmlImage
https://www.google.pt/gen_204?atyp=i&ct=mhp_asic&cad=&vet=10ahUKEwi7veTxkPznAhUJSq0KHX72BLAQ1MADCBI..s&ei=vildXrvmJomUtQX-7JOACw&zx=1583163839215
804 ms841 ms0 KB0 KB204text/htmlImage
https://www.google.pt/async/promos?ei=vildXrvmJomUtQX-7JOACw&yv=3&async=g:19016257,p:19016258,m:i,ic:1,_fmt:jspb
921 ms979 ms1 KB0 KB200application/jsonXHR
https://www.google.pt/fp_204?atyp=i&ct=&cad=&ptt=1&ptid=19016257&client=throttler&authuser=0&ei=vildXrvmJomUtQX-7JOACw&zx=1583163839339
928 ms974 ms1 KB0 KB200text/htmlImage
https://www.google.pt/gen_204?atyp=i&ct=14&cad=i&ogsr=1&id=19016258&ic=1&ogd=google.pt&ogprm=up&vet=10ahUKEwi7veTxkPznAhUJSq0KHX72BLAQjW0IAQ.vildXrvmJomUtQX-7JOACw.s&vis=1&ei=vildXrvmJomUtQX-7JOACw&zx=1583163839344
928 ms992 ms0 KB0 KB204text/htmlImage
https://www.gstatic.com/og/_/ss/k=og.mob.-1pfbx5fxsfgj4.L.W.O/m=md/excm=mih,mab,meb/d=1/ed=1/ct=zgms/rs=AA2YrTuu5Uuoh9qusE7aQv2bi07p2SR6kA
997 ms1002 ms3 KB15 KB200text/cssStylesheet
https://www.google.pt/gen_204?atyp=csi&ei=vildXrvmJomUtQX-7JOACw&s=webhp&t=all&bl=UTk5&imn=2&adh=&conn=onchange&ima=1&imad=0&ime=1&imex=2&imeh=0&imea=0&imeb=0&wh=660&scp=0&net=dl.10000,ect.4g,rtt.0&mem=ujhs.14,tjhs.45,jhsl.3760,dm.8&sto=&sys=hc.112&rt=iml.85,aft.85,prt.91,dcl.94,xjsls.98,xjses.380,xjsee.434,xjs.435,ol.666,wsrt.332,cst.0,dnst.0,rqst.156,rspt.0,rqstt.176,unt.176,cstt.176,dit.426&zx=1583163839417
1000 ms1013 ms0 KB0 KB-1Other
https://adservice.google.pt/adsid/google/ui
1011 ms1034 ms1 KB0 KB204text/htmlImage
Minimize third-party usage - Third-party code blocked the main thread for 0 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
32 KB0 ms
3 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
354 ms
8 ms
365 ms
10 ms
380 ms
17 ms
406 ms
10 ms
420 ms
15 ms
438 ms
9 ms
705 ms
82 ms
788 ms
37 ms
851 ms
60 ms
914 ms
34 ms
1014 ms
18 ms
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.

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

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.

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.pt/
http://www.google.pt/
https://www.google.pt/?gws_rd=ssl

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about ***% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Approximately ***% of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

https://www.gstatic.com/og/_/ss/k=og.mob.-1pfbx5fxsfgj4.L.W.O/m=md/excm=mih,mab,meb/d=1/ed=1/ct=zgms/rs=AA2YrTuu5Uuoh9qusE7aQv2bi07p2SR6kA
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.
Optimize images
Your images are optimized. Learn more about optimizing images.
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.pt use compression?

google.pt use gzip compression.
Original size: 46.6 KB
Compressed size: 15.53 KB
File reduced by: 31.07 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:
  89

+ SSL Checker - SSL Certificate Verify

google.pt 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: Feb 12 11:48:36 2020 GMT
Valid until: May 6 11:48:36 2020 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.pt supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Location: http://www.google.pt/
Content-Type: text/html; charset=UTF-8
Date: Fri, 06 Mar 2020 01:57:02 GMT
Expires: Sun, 05 Apr 2020 01:57:02 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, 06 Mar 2020 01:57:02 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: 15906
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Set-Cookie: 1P_JAR=2020-03-06-01; expires=Sun, 05-Apr-2020 01:57:02 GMT; path=/; domain=.google.pt; Secure
Set-Cookie: NID=199=mUT8LgIUrXOiR3r9TCkaTrjOuzpUfYp0VlyAknV8BEv-Itx4PZjg6HEF0OEoWq1qZN5ZevuP55bcmw29nFDKqCsmCzQP7eV2fk0nuShhVdwhv8qV-wPp0kSBwOnjMAFY3aMTP2bfy_o_-zhO6UFObcYLHv00Y88P00Rby_zrf-M; expires=Sat, 05-Sep-2020 01:57:02 GMT; path=/; domain=.google.pt; HttpOnly

+ DNS Lookup

Type Ip Target TTL
SOA 60
Mname ns1.google.com
Rname dns-admin.google.com
Serial Number 298808751
Refresh 900
Retry 900
Expire 1800
Minimum TTL 0
TXT 300
CAA 3600
MX alt3.aspmx.l.google.com 600
MX alt1.aspmx.l.google.com 600
MX aspmx.l.google.com 600
MX alt4.aspmx.l.google.com 600
MX alt2.aspmx.l.google.com 600
AAAA 300
A 172.217.4.35 300
NS ns1.google.com 3599
NS ns4.google.com 3599
NS ns2.google.com 3599
NS ns3.google.com 3599

+ Whois Lookup

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

whois lookup at whois.dns.pt...
\Error - could not open a connection to whois.dns.pt
Last update was 27 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

shikoserial.blogspot.com
3 secs
cointiply.com
25 secs
zendproxy.com
31 secs
serverboost.ml
1 min
zemula.org
1 min
videoara.mobi
1 min
sa-kra.ch
1 min
mangadropout.com
2 mins
app-vtube.com
2 mins
adbtc.top
2 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!
google.pt widget