goo.gl

goo.gl is SSL secured

Free website and domain report on goo.gl

Last Updated: 2nd April, 2023 Update Now
Overview

Snoop Summary for goo.gl

This is a free and comprehensive report about goo.gl. Goo.gl is hosted in United States on a server with an IP address of 172.253.115.101, where USD is the local currency and the local language is English. Our records indicate that goo.gl is owned/operated by Google LLC. Goo.gl is expected to earn an estimated $20,780 USD per day from advertising revenue. The sale of goo.gl would possibly be worth $15,169,503 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Goo.gl is unbelievably popular with an estimated 2,231,814 daily unique visitors. This report was last updated 2nd April, 2023.

About goo.gl

Site Preview: goo.gl goo.gl
Title: Google Developers Blog: Transitioning Google URL Shortener to Firebase Dynamic Links
Description: News and insights on Google platforms, tools, and events.
Keywords and Tags: 70th annual technology & engineering emmy awards, act contactos, beemovie com, calculus maximus, california gang map, glicko, internet services, navigate la, navigatela, popular, рутор орг поиск
Related Terms: goo, goo 86, goo gl, google shortener, shortener, ww goo, www goo, wwww goo
Fav Icon:
Age: Over 18 years old
Domain Created: 16th June, 2005
Domain Updated: 30th November, 2021
Domain Expires: 1st January, 2023
Review

Snoop Score

5/5 (Perfect!)

Valuation

$15,169,503 USD
Note: All valuation figures are estimates.

Popularity

Worldwide Sensation
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,111
Alexa Reach: 0.0596%
SEMrush Rank (US): 334,702
SEMrush Authority Score: 93
Moz Domain Authority: 94
Moz Page Authority: 86

Rank By Country

Country Alexa Rank
United Arab Emirates Flag United Arab Emirates 1,234
Argentina Flag Argentina 1,952
Austria Flag Austria 1,055
Australia Flag Australia 1,984
Belgium Flag Belgium 1,188
Brazil Flag Brazil 1,807
Canada Flag Canada 1,662
Switzerland Flag Switzerland 769
China Flag China 23,786
Czech Republic Flag Czech Republic 1,801
Germany Flag Germany 805
Spain Flag Spain 1,092
France Flag France 861
United Kingdom Flag United Kingdom 1,304
Greece Flag Greece 1,305
Indonesia Flag Indonesia 1,075
India Flag India 1,825
Italy Flag Italy 1,045
Japan Flag Japan 489
Korea Republic Of Flag Korea Republic Of 2,226
Mexico Flag Mexico 1,078
Malaysia Flag Malaysia 1,622
Netherlands Flag Netherlands 1,356
Poland Flag Poland 1,451
Romania Flag Romania 1,357
Russian Federation Flag Russian Federation 9,137
Saudi Arabia Flag Saudi Arabia 1,059
Singapore Flag Singapore 1,272
Thailand Flag Thailand 1,035
Turkey Flag Turkey 978
Taiwan, Province Of China Flag Taiwan, Province Of China 770
United States Flag United States 1,273
Viet Nam Flag Viet Nam 1,813
South Africa Flag South Africa 1,526

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 29,261 0
Traffic: 3,863 0
Cost: $564 USD $0 USD
Traffic

Visitors

Daily Visitors: 2,231,814
Monthly Visitors: 67,929,378
Yearly Visitors: 814,611,996
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
United Arab Emirates Flag United Arab Emirates Daily: 11,159
Monthly: 339,647
Yearly: 4,073,060
0.5%
Argentina Flag Argentina Daily: 17,855
Monthly: 543,435
Yearly: 6,516,896
0.8%
Austria Flag Austria Daily: 13,391
Monthly: 407,576
Yearly: 4,887,672
0.6%
Australia Flag Australia Daily: 22,318
Monthly: 679,294
Yearly: 8,146,120
1%
Belgium Flag Belgium Daily: 13,391
Monthly: 407,576
Yearly: 4,887,672
0.6%
Brazil Flag Brazil Daily: 58,027
Monthly: 1,766,164
Yearly: 21,179,912
2.6%
Canada Flag Canada Daily: 31,245
Monthly: 951,011
Yearly: 11,404,568
1.4%
Switzerland Flag Switzerland Daily: 13,391
Monthly: 407,576
Yearly: 4,887,672
0.6%
China Flag China Daily: 22,318
Monthly: 679,294
Yearly: 8,146,120
1%
Czech Republic Flag Czech Republic Daily: 11,159
Monthly: 339,647
Yearly: 4,073,060
0.5%
Germany Flag Germany Daily: 120,518
Monthly: 3,668,186
Yearly: 43,989,048
5.4%
Spain Flag Spain Daily: 53,564
Monthly: 1,630,305
Yearly: 19,550,688
2.4%
France Flag France Daily: 80,345
Monthly: 2,445,458
Yearly: 29,326,032
3.6%
United Kingdom Flag United Kingdom Daily: 69,186
Monthly: 2,105,811
Yearly: 25,252,972
3.1%
Greece Flag Greece Daily: 15,623
Monthly: 475,506
Yearly: 5,702,284
0.7%
Indonesia Flag Indonesia Daily: 42,404
Monthly: 1,290,658
Yearly: 15,477,628
1.9%
India Flag India Daily: 153,995
Monthly: 4,687,127
Yearly: 56,208,228
6.9%
Italy Flag Italy Daily: 60,259
Monthly: 1,834,093
Yearly: 21,994,524
2.7%
Japan Flag Japan Daily: 399,495
Monthly: 12,159,359
Yearly: 145,815,547
17.9%
Korea Republic Of Flag Korea Republic Of Daily: 37,941
Monthly: 1,154,799
Yearly: 13,848,404
1.7%
Mexico Flag Mexico Daily: 49,100
Monthly: 1,494,446
Yearly: 17,921,464
2.2%
Malaysia Flag Malaysia Daily: 13,391
Monthly: 407,576
Yearly: 4,887,672
0.6%
Netherlands Flag Netherlands Daily: 22,318
Monthly: 679,294
Yearly: 8,146,120
1%
Other Daily: 274,513
Monthly: 8,355,314
Yearly: 100,197,276
12.3%
Poland Flag Poland Daily: 29,014
Monthly: 883,082
Yearly: 10,589,956
1.3%
Romania Flag Romania Daily: 15,623
Monthly: 475,506
Yearly: 5,702,284
0.7%
Russian Federation Flag Russian Federation Daily: 11,159
Monthly: 339,647
Yearly: 4,073,060
0.5%
Saudi Arabia Flag Saudi Arabia Daily: 31,245
Monthly: 951,011
Yearly: 11,404,568
1.4%
Singapore Flag Singapore Daily: 13,391
Monthly: 407,576
Yearly: 4,887,672
0.6%
Thailand Flag Thailand Daily: 26,782
Monthly: 815,153
Yearly: 9,775,344
1.2%
Turkey Flag Turkey Daily: 42,404
Monthly: 1,290,658
Yearly: 15,477,628
1.9%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: 64,723
Monthly: 1,969,952
Yearly: 23,623,748
2.9%
United States Flag United States Daily: 361,554
Monthly: 11,004,559
Yearly: 131,967,143
16.2%
Viet Nam Flag Viet Nam Daily: 13,391
Monthly: 407,576
Yearly: 4,887,672
0.6%
South Africa Flag South Africa Daily: 17,855
Monthly: 543,435
Yearly: 6,516,896
0.8%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $20,780 USD
Monthly Revenue: $632,482 USD
Yearly Revenue: $7,584,746 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
United Arab Emirates Flag United Arab Emirates Daily: $13 USD
Monthly: $399 USD
Yearly: $4,782 USD
0.1%
Argentina Flag Argentina Daily: $4 USD
Monthly: $107 USD
Yearly: $1,287 USD
<0.1%
Austria Flag Austria Daily: $5 USD
Monthly: $156 USD
Yearly: $1,866 USD
<0.1%
Australia Flag Australia Daily: $59 USD
Monthly: $1,783 USD
Yearly: $21,378 USD
0.3%
Belgium Flag Belgium Daily: $7 USD
Monthly: $205 USD
Yearly: $2,459 USD
<0.1%
Brazil Flag Brazil Daily: $62 USD
Monthly: $1,888 USD
Yearly: $22,641 USD
0.3%
Canada Flag Canada Daily: $121 USD
Monthly: $3,694 USD
Yearly: $44,300 USD
0.6%
Switzerland Flag Switzerland Daily: $16 USD
Monthly: $492 USD
Yearly: $5,905 USD
0.1%
China Flag China Daily: $51 USD
Monthly: $1,546 USD
Yearly: $18,543 USD
0.2%
Czech Republic Flag Czech Republic Daily: $2 USD
Monthly: $46 USD
Yearly: $553 USD
<0.1%
Germany Flag Germany Daily: $694 USD
Monthly: $21,121 USD
Yearly: $253,285 USD
3.3%
Spain Flag Spain Daily: $72 USD
Monthly: $2,198 USD
Yearly: $26,360 USD
0.3%
France Flag France Daily: $256 USD
Monthly: $7,800 USD
Yearly: $93,536 USD
1.2%
United Kingdom Flag United Kingdom Daily: $494 USD
Monthly: $15,047 USD
Yearly: $180,444 USD
2.4%
Greece Flag Greece Daily: $5 USD
Monthly: $153 USD
Yearly: $1,829 USD
<0.1%
Indonesia Flag Indonesia Daily: $64 USD
Monthly: $1,941 USD
Yearly: $23,279 USD
0.3%
India Flag India Daily: $989 USD
Monthly: $30,105 USD
Yearly: $361,021 USD
4.8%
Italy Flag Italy Daily: $79 USD
Monthly: $2,412 USD
Yearly: $28,929 USD
0.4%
Japan Flag Japan Daily: $434 USD
Monthly: $13,212 USD
Yearly: $158,434 USD
2.1%
Korea Republic Of Flag Korea Republic Of Daily: $73 USD
Monthly: $2,208 USD
Yearly: $26,479 USD
0.3%
Mexico Flag Mexico Daily: $28 USD
Monthly: $848 USD
Yearly: $10,166 USD
0.1%
Malaysia Flag Malaysia Daily: $11 USD
Monthly: $328 USD
Yearly: $3,931 USD
0.1%
Netherlands Flag Netherlands Daily: $41 USD
Monthly: $1,245 USD
Yearly: $14,932 USD
0.2%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Poland Flag Poland Daily: $14 USD
Monthly: $418 USD
Yearly: $5,016 USD
0.1%
Romania Flag Romania Daily: $3 USD
Monthly: $93 USD
Yearly: $1,117 USD
<0.1%
Russian Federation Flag Russian Federation Daily: $4 USD
Monthly: $134 USD
Yearly: $1,605 USD
<0.1%
Saudi Arabia Flag Saudi Arabia Daily: $16 USD
Monthly: $472 USD
Yearly: $5,658 USD
0.1%
Singapore Flag Singapore Daily: $6 USD
Monthly: $181 USD
Yearly: $2,174 USD
<0.1%
Thailand Flag Thailand Daily: $14 USD
Monthly: $411 USD
Yearly: $4,930 USD
0.1%
Turkey Flag Turkey Daily: $33 USD
Monthly: $1,014 USD
Yearly: $12,159 USD
0.2%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: $12 USD
Monthly: $359 USD
Yearly: $4,306 USD
0.1%
United States Flag United States Daily: $17,062 USD
Monthly: $519,305 USD
Yearly: $6,227,533 USD
82.1%
Viet Nam Flag Viet Nam Daily: $8 USD
Monthly: $230 USD
Yearly: $2,762 USD
<0.1%
South Africa Flag South Africa Daily: $31 USD
Monthly: $930 USD
Yearly: $11,149 USD
0.1%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Backlinks: 2,464,678,657
Referring Domains: 2,789,049
Referring IPs: 1,046,306
Goo.gl has 2,464,678,657 backlinks according to SEMrush. 84% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve goo.gl's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of goo.gl's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://www.defisurbains.fr/
Target: https://goo.gl/maps/4TBquC8RRGhFpDZS7

2
Source: https://americanheroesnetwork.com/
Target: https://playmusic.app.goo.gl/?apn=com.google.android.music&ibi=com.google.PlayMusic&isi=691797987&ius=googleplaymusic&link=https%3A%2F%2Fplay.google.com%2Fmusic%2Fm%2FIscdw6s4heodraklztiyeikshqe%3Ft%3DThe_American_Heroes_Network_Podcast%26pcampaignid%3DMKT-na-all-co-pr-mu-pod-16

3
Source: https://americanheroesnetwork.com/
Target: https://playmusic.app.goo.gl/?apn=com.google.android.music&ibi=com.google.PlayMusic&isi=691797987&ius=googleplaymusic&link=https%3A%2F%2Fplay.google.com%2Fmusic%2Fm%2FIscdw6s4heodraklztiyeikshqe%3Ft%3DThe_American_Heroes_Network_Podcast%26pcampaignid%3DMKT-na-all-co-pr-mu-pod-16

4
Source: http://night2.icu/
Target: https://goo.gl/

5
Source: http://coat1.pw/
Target: https://goo.gl/

Top Ranking Keywords (US)

1
Keyword: california gang map
Ranked Page: https://goo.gl/maps/bGiLJSv7uM62

2
Keyword: beemovie com
Ranked Page: https://goo.gl/ZkB3x4

3
Keyword: california gang map
Ranked Page: https://goo.gl/eXK2qH

4
Keyword: navigatela
Ranked Page: http://goo.gl/ZEWnwn

5
Keyword: calculus maximus
Ranked Page: http://goo.gl/rLZUNM

Domain Analysis

Value Length
Domain: goo.gl 6
Domain Name: goo 3
Extension (TLD): gl 2
Expiry Check:

Page Speed Analysis

Average Load Time: 0.49 seconds
Load Time Comparison: Faster than 95% of sites

PageSpeed Insights

Avg. (All Categories) 75
Performance 93
Accessibility 0
Best Practices 92
SEO 92
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html
Updated: 2nd November, 2022

1.49 seconds
First Contentful Paint (FCP)
81%
12%
7%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
93

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for goo.gl. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 1.3 s
The time taken for the page to become fully interactive.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://goo.gl/
http/1.1
0
12.097000144422
408
0
301
application/binary
https://goo.gl/
http/1.1
12.462000362575
45.794000383466
1789
0
301
application/binary
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html
h2
46.26000020653
140.45500010252
13285
59849
200
text/html
Document
https://www.blogger.com/static/v1/widgets/2975350028-css_bundle_v2.css
h2
149.7780000791
158.44800043851
8578
35960
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Google+Sans:400,500,700|Google+Sans+Display:400,500,600,700|Roboto:400,400italic,500,500italic,700,700italic|Roboto+Mono:400,500,700|Material+Icons
h2
150.37700021639
161.6200003773
2884
37464
200
text/css
Stylesheet
https://www.gstatic.com/devrel-devsite/prod/v0a713fec70a4b4c54311265d5142e962747a0e45a24063467564a2765c008ac7/developers/images/lockup-developers.svg
h2
169.79700000957
176.09200021252
3267
6014
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_youtube.svg
h2
174.77500019595
179.69000013545
1065
425
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_twitter.svg
h2
174.94700010866
182.50400014222
1089
515
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_instagram.svg
h2
175.17000017688
182.9119999893
1432
1674
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_linkedin.svg
h2
175.61200028285
184.73100010306
1301
1152
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_facebook.svg
h2
175.94700027257
186.15700025111
1163
757
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_twitter_black.svg
h2
177.05900035799
185.10600039735
1266
966
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_facebook_black.svg
h2
177.51900013536
184.34600019827
1135
672
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_linkedin_black.svg
h2
177.77000041679
185.46700011939
1267
1082
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_mail.svg
h2
177.99200024456
185.80500036478
1004
283
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_link.svg
h2
178.17600024864
186.75100011751
1061
415
200
image/svg+xml
Image
https://www.blogger.com/static/v1/widgets/1836859926-widgets.js
h2
163.14100008458
171.85100028291
57635
157594
200
text/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-WVTLDSL
h2
178.39300027117
192.00200028718
47863
120740
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
178.53300040588
183.4560004063
20664
50230
200
text/javascript
Script
https://www.blogger.com/dyn-css/authorization.css?targetBlogID=596098824972435195&zx=6dc12e80-9f07-46c8-9e40-215eeb632f6b
h2
178.8110001944
188.27200029045
1217
1
200
text/css
Stylesheet
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
193.1920000352
196.43700029701
11999
11072
200
font/woff2
Font
https://fonts.gstatic.com/s/materialicons/v139/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
h2
193.65000026301
198.36300006136
129288
128360
200
font/woff2
Font
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBkXYtBD7TL5-PQE.woff2
h2
194.02500009164
198.83500039577
15516
14588
200
font/woff2
Font
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBg3etBD7TL5-PQE.woff2
h2
194.1890004091
197.89599999785
15636
14708
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
199.94200021029
203.14500015229
11956
11028
200
font/woff2
Font
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79oT3ZQZQ.woff2
h2
260.7010002248
264.01300029829
15472
14544
200
font/woff2
Font
https://fonts.gstatic.com/s/robotomono/v22/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2
h2
260.92800032347
265.30900038779
23068
22140
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
h2
261.23600034043
264.92100022733
13612
12684
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
261.50800008327
264.47100006044
11968
11040
200
font/woff2
Font
https://www.blogger.com/dyn-css/authorization.css?targetBlogID=596098824972435195&zx=6dc12e80-9f07-46c8-9e40-215eeb632f6b
h2
289.17900007218
303.11600025743
1217
1
200
text/css
Stylesheet
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=606862801&t=pageview&_s=1&dl=https%3A%2F%2Fdevelopers.googleblog.com%2F2018%2F03%2Ftransitioning-google-url-shortener.html&ul=en-us&de=UTF-8&dt=Google%20Developers%20Blog%3A%20Transitioning%20Google%20URL%20Shortener%20to%20Firebase%20Dynamic%20Links&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAACAAI~&jid=1357391014&gjid=1173075298&cid=1702668158.1667393232&tid=UA-19996418-48&_gid=698074896.1667393232&_r=1&_slc=1&z=1365150606
h2
382.50300008804
386.14800013602
626
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-19996418-48&cid=1702668158.1667393232&jid=1357391014&gjid=1173075298&_gid=698074896.1667393232&_u=IEBAAEAAAAAAACAAI~&z=395257605
h2
390.2800003998
394.36400029808
696
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
145.412
15.877
162.782
6.759
180.164
28.938
243.051
10.655
259.412
28.514
294.186
19.517
320.963
9.301
330.921
18.408
354.421
5.454
360.011
24.192
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Goo.gl should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Goo.gl should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Goo.gl should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Goo.gl should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Goo.gl should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 72 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.blogger.com/static/v1/widgets/1836859926-widgets.js
57635
42880
https://www.googletagmanager.com/gtm.js?id=GTM-WVTLDSL
47863
30669
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 100 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html
95.189
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Goo.gl should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 411 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://fonts.gstatic.com/s/materialicons/v139/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
129288
https://www.blogger.com/static/v1/widgets/1836859926-widgets.js
57635
https://www.googletagmanager.com/gtm.js?id=GTM-WVTLDSL
47863
https://fonts.gstatic.com/s/robotomono/v22/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2
23068
https://www.google-analytics.com/analytics.js
20664
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBg3etBD7TL5-PQE.woff2
15636
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBkXYtBD7TL5-PQE.woff2
15516
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79oT3ZQZQ.woff2
15472
https://fonts.gstatic.com/s/roboto/v30/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
13612
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html
13285
Uses efficient cache policy on static assets — 1 resource found
Goo.gl can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20664
Avoids an excessive DOM size — 222 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
222
Maximum DOM Depth
10
Maximum Child Elements
13
Avoid chaining critical requests — 11 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Goo.gl should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html
126.55
13.062
3.236
Unattributable
64.105
2.371
0
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
82.109
Style & Layout
64.257
Script Evaluation
62.305
Parse HTML & CSS
16.034
Rendering
14.073
Script Parsing & Compilation
9.886
Garbage Collection
2.495
Keep request counts low and transfer sizes small — 32 requests • 411 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
32
420427
Font
9
248515
Script
3
126162
Image
11
15050
Stylesheet
4
13896
Document
1
13285
Other
4
3519
Media
0
0
Third-party
31
407142
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
251399
0
68647
0
47863
0
21290
0
15050
0
696
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00086491330147767
0.00084432012763296
0.00045550073086743
0.00039127030304942
0.00013258324844891
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of goo.gl on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.2 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.3 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 1.3 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 610 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Goo.gl should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.blogger.com/static/v1/widgets/2975350028-css_bundle_v2.css
8578
230
https://fonts.googleapis.com/css?family=Google+Sans:400,500,700|Google+Sans+Display:400,500,600,700|Roboto:400,400italic,500,500italic,700,700italic|Roboto+Mono:400,500,700|Material+Icons
2884
230
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Goo.gl should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://goo.gl/
190
https://goo.gl/
150
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html
0

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
3.2450002618134
https://fonts.gstatic.com/s/materialicons/v139/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
4.7129997983575
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBkXYtBD7TL5-PQE.woff2
4.8100003041327
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBg3etBD7TL5-PQE.woff2
3.7069995887578
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.2029999420047
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79oT3ZQZQ.woff2
3.3120000734925
https://fonts.gstatic.com/s/robotomono/v22/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2
4.3810000643134
https://fonts.gstatic.com/s/roboto/v30/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
3.6849998869002
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
2.9629999771714
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.gstatic.com/dgc_blog/images/ic_youtube.svg
https://www.gstatic.com/dgc_blog/images/ic_twitter.svg
https://www.gstatic.com/devrel-devsite/prod/v0a713fec70a4b4c54311265d5142e962747a0e45a24063467564a2765c008ac7/developers/images/lockup-developers.svg
https://www.gstatic.com/devrel-devsite/prod/v0a713fec70a4b4c54311265d5142e962747a0e45a24063467564a2765c008ac7/developers/images/lockup-developers.svg
https://www.gstatic.com/dgc_blog/images/ic_twitter_black.svg
https://www.gstatic.com/dgc_blog/images/ic_facebook_black.svg
https://www.gstatic.com/dgc_blog/images/ic_linkedin_black.svg
https://www.gstatic.com/dgc_blog/images/ic_mail.svg
https://www.gstatic.com/dgc_blog/images/ic_link.svg
https://www.gstatic.com/dgc_blog/images/ic_instagram.svg
https://www.gstatic.com/dgc_blog/images/ic_linkedin.svg
https://www.gstatic.com/dgc_blog/images/ic_facebook.svg
0

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of goo.gl. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Goo.gl may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Tables and lists

List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that goo.gl should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://goo.gl/
Allowed
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for goo.gl. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of goo.gl on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of goo.gl. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of goo.gl on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 70
Performance 69
Accessibility 0
Best Practices 92
SEO 89
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html
Updated: 2nd November, 2022

2.55 seconds
First Contentful Paint (FCP)
59%
23%
18%

0.02 seconds
First Input Delay (FID)
95%
4%
1%

Simulate loading on mobile
69

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for goo.gl. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://goo.gl/
http/1.1
0
14.419999904931
409
0
301
application/binary
https://goo.gl/
http/1.1
14.784000115469
47.157000051811
1970
0
301
application/binary
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html
http/1.1
47.767000040039
68.808000069112
740
0
302
text/html
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html?m=1
h2
69.407999981195
285.75900010765
13282
59848
200
text/html
Document
https://www.blogger.com/static/v1/widgets/2975350028-css_bundle_v2.css
h2
297.49900009483
306.79999990389
8579
35960
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Google+Sans:400,500,700|Google+Sans+Display:400,500,600,700|Roboto:400,400italic,500,500italic,700,700italic|Roboto+Mono:400,500,700|Material+Icons
h2
298.45399991609
327.1989999339
2985
40544
200
text/css
Stylesheet
https://www.gstatic.com/devrel-devsite/prod/v0a713fec70a4b4c54311265d5142e962747a0e45a24063467564a2765c008ac7/developers/images/lockup-developers.svg
h2
330.11500001885
335.41900012642
3280
6014
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_youtube.svg
h2
334.23499995843
341.02699998766
1052
425
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_twitter.svg
h2
336.4349999465
351.26299993135
1089
515
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_instagram.svg
h2
336.8120000232
349.72400008701
1445
1674
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_linkedin.svg
h2
337.55500009283
349.34900002554
1301
1152
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_facebook.svg
h2
338.53600011207
347.76900010183
1172
757
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_twitter_black.svg
h2
339.05600011349
348.93400012515
1266
966
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_facebook_black.svg
h2
339.18799995445
348.6790000461
1148
672
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_linkedin_black.svg
h2
340.44800000265
350.66700004973
1267
1082
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_mail.svg
h2
340.79500008374
352.31600003317
1004
283
200
image/svg+xml
Image
https://www.gstatic.com/dgc_blog/images/ic_link.svg
h2
340.91700008139
351.5409999527
1061
415
200
image/svg+xml
Image
https://www.blogger.com/static/v1/widgets/1836859926-widgets.js
h2
311.98400002904
321.66799996048
57635
157594
200
text/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-WVTLDSL
h2
341.99000010267
358.21900004521
47862
120740
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
342.16800006106
350.12999991886
20664
50230
200
text/javascript
Script
https://www.blogger.com/dyn-css/authorization.css?targetBlogID=596098824972435195&zx=6dc12e80-9f07-46c8-9e40-215eeb632f6b
h2
342.30699995533
353.05700008757
1217
1
200
text/css
Stylesheet
https://fonts.gstatic.com/s/materialicons/v139/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
h2
350.58799991384
357.62199992314
129288
128360
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
353.45000005327
358.69699995965
12000
11072
200
font/woff2
Font
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBg3etBD7TL5-PQE.woff2
h2
354.09800009802
359.1440001037
15636
14708
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
360.02300004475
365.46900006942
11955
11028
200
font/woff2
Font
https://fonts.gstatic.com/s/robotomono/v22/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2
h2
411.47499997169
415.16300011426
23068
22140
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
h2
413.55900000781
417.05900011584
13612
12684
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
415.62400013208
419.68700010329
11968
11040
200
font/woff2
Font
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBkXYtBD7TL5-PQE.woff2
h2
415.98300007172
422.05099994317
15516
14588
200
font/woff2
Font
https://www.blogger.com/dyn-css/authorization.css?targetBlogID=596098824972435195&zx=6dc12e80-9f07-46c8-9e40-215eeb632f6b
h2
451.02600008249
463.51599995978
1217
1
200
text/css
Stylesheet
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79oT3ZQZQ.woff2
h2
460.77700005844
464.13500001654
15472
14544
200
font/woff2
Font
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=139197826&t=pageview&_s=1&dl=https%3A%2F%2Fdevelopers.googleblog.com%2F2018%2F03%2Ftransitioning-google-url-shortener.html%3Fm%3D1&ul=en-us&de=UTF-8&dt=Google%20Developers%20Blog%3A%20Transitioning%20Google%20URL%20Shortener%20to%20Firebase%20Dynamic%20Links&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAACAAI~&jid=1971853615&gjid=641303736&cid=678278301.1667393251&tid=UA-19996418-48&_gid=1631224130.1667393251&_r=1&_slc=1&z=359777238
h2
558.82199993357
564.1389999073
626
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-19996418-48&cid=678278301.1667393251&jid=1971853615&gjid=641303736&_gid=1631224130.1667393251&_u=IEBAAEAAAAAAACAAI~&z=1410010383
h2
569.34299995191
573.83999996819
696
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
291.197
14.004
338.92
27.588
395.207
11.564
410.441
29.246
440.686
8.901
460.866
20.672
481.556
17.887
501.171
10.455
514.732
11.988
533.549
27.069
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Goo.gl should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Goo.gl should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Goo.gl should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Goo.gl should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Goo.gl should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 220 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html?m=1
217.344
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Goo.gl should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 412 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://fonts.gstatic.com/s/materialicons/v139/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
129288
https://www.blogger.com/static/v1/widgets/1836859926-widgets.js
57635
https://www.googletagmanager.com/gtm.js?id=GTM-WVTLDSL
47862
https://fonts.gstatic.com/s/robotomono/v22/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2
23068
https://www.google-analytics.com/analytics.js
20664
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBg3etBD7TL5-PQE.woff2
15636
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBkXYtBD7TL5-PQE.woff2
15516
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79oT3ZQZQ.woff2
15472
https://fonts.gstatic.com/s/roboto/v30/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
13612
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html?m=1
13282
Uses efficient cache policy on static assets — 1 resource found
Goo.gl can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20664
Avoids an excessive DOM size — 222 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
222
Maximum DOM Depth
10
Maximum Child Elements
13
Avoid chaining critical requests — 11 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Goo.gl should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html?m=1
523.804
44.696
13.88
Unattributable
280.532
9.028
0
https://www.google-analytics.com/analytics.js
122.632
108.348
4.784
https://www.googletagmanager.com/gtm.js?id=GTM-WVTLDSL
68.396
55.508
8.98
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
361.036
Style & Layout
305.94
Script Evaluation
245.328
Parse HTML & CSS
58.868
Rendering
52.756
Script Parsing & Compilation
42.576
Keep request counts low and transfer sizes small — 33 requests • 412 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
33
421482
Font
9
248515
Script
3
126161
Image
11
15085
Stylesheet
4
13998
Document
1
13282
Other
5
4441
Media
0
0
Third-party
31
407460
Minimize third-party usage — Third-party code blocked the main thread for 50 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
21290
50.984
251500
0
68648
0
47862
0
15085
0
696
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00019792556762695
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google-analytics.com/analytics.js
3300
108
https://www.blogger.com/static/v1/widgets/1836859926-widgets.js
4350
72
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html?m=1
2181
58
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html?m=1
2070
56
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html?m=1
2126
55
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of goo.gl on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Time to Interactive — 4.8 s
The time taken for the page to become fully interactive.
Speed Index — 4.5 s
The time taken for the page contents to be visibly populated.

Other

Reduce unused JavaScript — Potential savings of 72 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.blogger.com/static/v1/widgets/1836859926-widgets.js
57635
42880
https://www.googletagmanager.com/gtm.js?id=GTM-WVTLDSL
47862
30668

Metrics

First Contentful Paint — 4.5 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 4.8 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 4.8 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 2,410 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Goo.gl should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.blogger.com/static/v1/widgets/2975350028-css_bundle_v2.css
8579
780
https://fonts.googleapis.com/css?family=Google+Sans:400,500,700|Google+Sans+Display:400,500,600,700|Roboto:400,400italic,500,500italic,700,700italic|Roboto+Mono:400,500,700|Material+Icons
2985
780
Avoid multiple page redirects — Potential savings of 1,890 ms
Redirects can cause additional delays before the page can begin loading. Goo.gl should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://goo.gl/
630
https://goo.gl/
480
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html
780
https://developers.googleblog.com/2018/03/transitioning-google-url-shortener.html?m=1
0
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/materialicons/v139/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
7.0340000092983
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
5.246999906376
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBg3etBD7TL5-PQE.woff2
5.0460000056773
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
5.4460000246763
https://fonts.gstatic.com/s/robotomono/v22/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5Ese6hmHSh0me8iUI0.woff2
3.6880001425743
https://fonts.gstatic.com/s/roboto/v30/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
3.5000001080334
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
4.062999971211
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBkXYtBD7TL5-PQE.woff2
6.0679998714477
https://fonts.gstatic.com/s/googlesansdisplay/v21/ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79oT3ZQZQ.woff2
3.3579999580979
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.gstatic.com/devrel-devsite/prod/v0a713fec70a4b4c54311265d5142e962747a0e45a24063467564a2765c008ac7/developers/images/lockup-developers.svg
https://www.gstatic.com/devrel-devsite/prod/v0a713fec70a4b4c54311265d5142e962747a0e45a24063467564a2765c008ac7/developers/images/lockup-developers.svg
https://www.gstatic.com/dgc_blog/images/ic_twitter_black.svg
https://www.gstatic.com/dgc_blog/images/ic_facebook_black.svg
https://www.gstatic.com/dgc_blog/images/ic_linkedin_black.svg
https://www.gstatic.com/dgc_blog/images/ic_mail.svg
https://www.gstatic.com/dgc_blog/images/ic_link.svg
First Contentful Paint (3G) — 8880 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
0

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of goo.gl. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Goo.gl may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Tables and lists

List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that goo.gl should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://goo.gl/
Allowed
89

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for goo.gl. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of goo.gl on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Mobile Friendly

Tap targets are not sized appropriately — 54% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
28x16
44x16
44x16
50x16
125x16
157x16
78x16
78x16
122x16
194x16
127x16
106x16
166x16
175x16

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
30

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of goo.gl. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of goo.gl on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 172.253.115.101
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Google LLC
Country: US
City:
State: CA
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
MarkMonitor Inc. 104.18.39.152
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 93/100
WOT Child Safety: 93/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: misc-sni.google.com
Issued By: GTS CA 1C3
Valid From: 17th October, 2022
Valid To: 9th January, 2023
Subject: CN = misc-sni.google.com
Hash: 4e5dd0a0
Issuer: CN = GTS CA 1C3
O = Google Trust Services LLC
S = US
Version: 2
Serial Number: 0x853554F98D49C77D127D38B862F91E7F
Serial Number (Hex): 853554F98D49C77D127D38B862F91E7F
Valid From: 17th October, 2024
Valid To: 9th January, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:8A:74:7F:AF:85:CD:EE:95:CD:3D:9C:D0:E2:46:14:F3:71:35:1D:27
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://crls.pki.goog/gts1c3/moVDfISia2k.crl

Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.11129.2.5.3

Authority Information Access: OCSP - URI:http://ocsp.pki.goog/gts1c3
CA Issuers - URI:http://pki.goog/repo/certs/gts1c3.der

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Oct 17 09:18:04.881 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:BF:10:E1:CF:24:9A:A0:90:74:8D:E3:
CA:FE:26:54:5D:A6:44:CF:90:DB:62:A1:F9:51:DE:9C:
50:E7:C1:67:72:02:21:00:B7:77:94:CA:30:D5:C2:1C:
FD:BA:9E:B8:74:94:A5:7F:9F:EE:B1:AD:64:21:CD:FA:
3D:34:0A:F7:2C:FB:92:A0
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Oct 17 09:18:04.816 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C0:9C:86:20:99:BE:B2:24:02:AB:CF:
B7:9B:DE:0B:FE:6F:05:10:9B:12:21:B9:16:6F:6F:F4:
FB:3A:8F:EB:B8:02:21:00:AE:E0:6D:68:58:AB:1F:F8:
7C:30:80:BC:8A:EA:9D:05:C8:19:D5:9D:91:BD:2B:ED:
AD:80:F2:BF:F1:C5:0D:0C
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.1ucrs.com
DNS:*.abc.xyz
DNS:*.adsensecustomsearchads.com
DNS:*.advertisercommunity.com
DNS:*.aiplatform-training.cloud.google.com
DNS:*.ampcache.com
DNS:*.ampproject.com
DNS:*.ampproject.net
DNS:*.ampproject.org
DNS:*.androidify.com
DNS:*.app.goo.gl
DNS:*.backstory-staging.chronicle.security
DNS:*.backstory.chronicle.security
DNS:*.backstory.chroniclesec.com
DNS:*.backupdr-autopush.cloud.google.com
DNS:*.backupdr-dev.cloud.google.com
DNS:*.backupdr-staging.cloud.google.com
DNS:*.backupdr.cloud.google.com
DNS:*.brocaproject.com
DNS:*.cdn.ampproject.org
DNS:*.chronicle.security
DNS:*.chronicleforgood.com
DNS:*.chroniclesec.com
DNS:*.cloud.google
DNS:*.cloudyoryx.dev
DNS:*.composer-dev.cloud.google.com
DNS:*.composer-qa.cloud.google.com
DNS:*.composer-staging.cloud.google.com
DNS:*.composer.cloud.google.com
DNS:*.crossmediapanel.com
DNS:*.datafusion-api-dev.cloud.google.com
DNS:*.datafusion-api-staging.cloud.google.com
DNS:*.datafusion-api.cloud.google.com
DNS:*.datafusion-dev.cloud.google.com
DNS:*.datafusion-staging.cloud.google.com
DNS:*.datafusion.cloud.google.com
DNS:*.datalab.cloud.google.com
DNS:*.dataliberation.org
DNS:*.dataplex-dev.cloud.google.com
DNS:*.dataplex-staging.cloud.google.com
DNS:*.dataplex.cloud.google.com
DNS:*.dataproc-image-staging.cloud.google.com
DNS:*.dataproc-staging.cloud.google.com
DNS:*.dataproc-test.cloud.google.com
DNS:*.dataproc.cloud.google.com
DNS:*.de.advertisercommunity.com
DNS:*.de.gateway.dev
DNS:*.dev.google-syndication.com
DNS:*.digitalassetlinks.org
DNS:*.domains.google
DNS:*.earlydays.google
DNS:*.earthengine.google.co.in
DNS:*.earthengine.google.com
DNS:*.en.advertisercommunity.com
DNS:*.es.advertisercommunity.com
DNS:*.ew.gateway.dev
DNS:*.fiber.google.com
DNS:*.floonet.goog
DNS:*.fr.advertisercommunity.com
DNS:*.g.dev
DNS:*.g.page
DNS:*.gateway.dev
DNS:*.gmbads.gle
DNS:*.go-lang.com
DNS:*.go-lang.net
DNS:*.go-lang.org
DNS:*.golang.com
DNS:*.golang.google.cn
DNS:*.golang.net
DNS:*.golang.org
DNS:*.google-syndication.com
DNS:*.googleacquisitionmigration.com
DNS:*.googleblog.com
DNS:*.googlecert.net
DNS:*.grow.google
DNS:*.gvt5.com
DNS:*.hats.goog
DNS:*.healthcare.cloud.google.com
DNS:*.hey.gle
DNS:*.id.advertisercommunity.com
DNS:*.it.advertisercommunity.com
DNS:*.ja.advertisercommunity.com
DNS:*.lanternal.com
DNS:*.liftware.com
DNS:*.liftware.jp
DNS:*.looker.chronicle.security
DNS:*.macservice.goog
DNS:*.mapmaker.google.com
DNS:*.microhost.google.com
DNS:*.nel.goog
DNS:*.nomulus.foo
DNS:*.notebooks.cloud.google.com
DNS:*.ok.gle
DNS:*.ordering.page
DNS:*.picasaweb.com
DNS:*.picasaweb.net
DNS:*.picasaweb.org
DNS:*.picnik.com
DNS:*.pipelines.cloud.google.com
DNS:*.pki.goog
DNS:*.pl.advertisercommunity.com
DNS:*.play.space
DNS:*.podcasts.goog
DNS:*.pt.advertisercommunity.com
DNS:*.rbm.goog
DNS:*.recaptcha.ampproject.net
DNS:*.research.youtube
DNS:*.ru.advertisercommunity.com
DNS:*.savethedate.foo
DNS:*.searchingforsyria.org
DNS:*.songwriters.youtube
DNS:*.source.bazel.build
DNS:*.stage.advertisercommunity.com
DNS:*.staging.google-syndication.com
DNS:*.tensorboard-autopush.cloud.google.com
DNS:*.tensorboard-dev.cloud.google.com
DNS:*.tensorboard-staging.cloud.google.com
DNS:*.tensorboard-test.cloud.google.com
DNS:*.tensorboard.cloud.google.com
DNS:*.tfhub.dev
DNS:*.th.advertisercommunity.com
DNS:*.tiltbrush.com
DNS:*.travel.google
DNS:*.uc.gateway.dev
DNS:*.vi.advertisercommunity.com
DNS:*.webmproject.org
DNS:*.webpkgcache.com
DNS:*.xn--9kr7l.com
DNS:*.xn--flw351e.com
DNS:*.xn--ggle-55da.com
DNS:*.xn--gogl-0nd52e.com
DNS:*.xn--gogl-1nd42e.com
DNS:*.xn--ngstr-lra8j.com
DNS:*.xplr.co
DNS:*.zh.advertisercommunity.com
DNS:*.zynamics.com
DNS:1ucrs.com
DNS:abc.xyz
DNS:admin.health.google.com
DNS:adsense.com
DNS:adsensecustomsearchads.com
DNS:adsenseformobileapps.com
DNS:advertisercommunity.com
DNS:ampcache.com
DNS:ampproject.com
DNS:ampproject.net
DNS:ampproject.org
DNS:androidify.com
DNS:app.goo.gl
DNS:brocaproject.com
DNS:bugs.webrtc.org
DNS:channel-app.google
DNS:chronicle.security
DNS:chronicleforgood.com
DNS:chroniclesec.com
DNS:cloud.google
DNS:cloudyoryx.dev
DNS:code.webrtc.org
DNS:colab-sandbox.research.google.com
DNS:colab.research.google.com
DNS:crossmediapanel.com
DNS:dataliberation.org
DNS:datasetsearch.research.google.com
DNS:de.advertisercommunity.com
DNS:deepmind.com
DNS:dg-meta.video.google.com
DNS:digitalassetlinks.org
DNS:domains.google
DNS:earlydays.google
DNS:ehr-search.health.google.com
DNS:en.advertisercommunity.com
DNS:es.advertisercommunity.com
DNS:fastlane.ci
DNS:floonet.goog
DNS:fr.advertisercommunity.com
DNS:g.dev
DNS:g.page
DNS:gapi.waze.com
DNS:gmbads.gle
DNS:go-lang.com
DNS:go-lang.net
DNS:go-lang.org
DNS:golang.com
DNS:golang.google.cn
DNS:golang.net
DNS:golang.org
DNS:googleblog.com
DNS:googlecert.net
DNS:googlestore.com
DNS:grow.google
DNS:hats.goog
DNS:hey.gle
DNS:iamremarkable.org
DNS:id.advertisercommunity.com
DNS:it.advertisercommunity.com
DNS:ja.advertisercommunity.com
DNS:lanternal.com
DNS:legalretrievals.google
DNS:lers.google
DNS:liftware.com
DNS:liftware.jp
DNS:looker.chronicle.security
DNS:macservice.goog
DNS:nel.goog
DNS:nomulus.foo
DNS:ok.gle
DNS:ordering.page
DNS:pagespeed.web.dev
DNS:picasaweb.com
DNS:picasaweb.net
DNS:picasaweb.org
DNS:picnik.com
DNS:pixate.com
DNS:pki.goog
DNS:pl.advertisercommunity.com
DNS:play.space
DNS:pt.advertisercommunity.com
DNS:rbm.goog
DNS:registry-qa.google
DNS:registry-sandbox.google
DNS:registry.google
DNS:research.youtube
DNS:ru.advertisercommunity.com
DNS:savethedate.foo
DNS:searchingforsyria.org
DNS:songwriters.youtube
DNS:source.bazel.build
DNS:sprayscape.com
DNS:stage.advertisercommunity.com
DNS:support.registry-qa.google
DNS:support.registry-sandbox.google
DNS:support.registry.google
DNS:tfhub.dev
DNS:th.advertisercommunity.com
DNS:thegooglestore.com
DNS:tiltbrush.com
DNS:travel.google
DNS:vi.advertisercommunity.com
DNS:webmproject.org
DNS:webpkgcache.com
DNS:www.adsense.com
DNS:www.deepmind.com
DNS:www.googlestore.com
DNS:www.iamremarkable.org
DNS:www.pixate.com
DNS:www.registry-qa.google
DNS:www.registry-sandbox.google
DNS:www.registry.google
DNS:www.sprayscape.com
DNS:www.thegooglestore.com
DNS:xn--9kr7l.com
DNS:xn--flw351e.com
DNS:xn--ggle-55da.com
DNS:xn--gogl-0nd52e.com
DNS:xn--gogl-1nd42e.com
DNS:xn--ngstr-lra8j.com
DNS:xplr.co
DNS:zh.advertisercommunity.com
DNS:zynamics.com
DNS:misc-sni.google.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
goo.gl. 142.251.163.138 IN 300
goo.gl. 142.251.163.139 IN 300
goo.gl. 142.251.163.100 IN 300
goo.gl. 142.251.163.102 IN 300
goo.gl. 142.251.163.113 IN 300
goo.gl. 142.251.163.101 IN 300

NS Records

Host Nameserver Class TTL
goo.gl. ns1.google.com. IN 21600
goo.gl. ns4.google.com. IN 21600
goo.gl. ns2.google.com. IN 21600
goo.gl. ns3.google.com. IN 21600

AAAA Records

IP Address Class TTL
2607:f8b0:4004:c1b::64 IN 300
2607:f8b0:4004:c1b::8b IN 300
2607:f8b0:4004:c1b::66 IN 300
2607:f8b0:4004:c1b::8a IN 300

CAA Records

Domain Flags Tag Class TTL
pki.goog 0 issue IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
goo.gl. ns1.google.com. dns-admin.google.com. 60

TXT Records

Host Value Class TTL
goo.gl. facebook-domain-verification=7o3yquoyjiue2na6brk0mxzcxqb9w7 IN 300
goo.gl. v=spf1 IN 300

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Expires: 7th November, 2022
Date: 7th November, 2022
Cache-Control: private, max-age=0
Server: GSE
Strict-Transport-Security: max-age=86400; includeSubDomains
Last-Modified: 7th November, 2022
ETag: W/"8adc81942b9d3e9cb5db9424a3b8761f33728cb6938cb72414e4d41584fa0f67"
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 0
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"

Whois Lookup

Created: 16th June, 2005
Changed: 30th November, 2021
Expires: 1st January, 2023
Registrar: MarkMonitor, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
Nameservers: ns1.google.com
ns2.google.com
ns3.google.com
ns4.google.com
Owner Organization: Google LLC
Owner State: CA
Owner Country: US
Owner Email: Select Request Email Form at https://domains.markmonitor.com/whois/goo.gl
Admin Organization: Google LLC
Admin State: CA
Admin Country: US
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/goo.gl
Tech Organization: Google LLC
Tech State: CA
Tech Country: US
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/goo.gl
Full Whois: Domain Name: goo.gl
Registry Domain ID:
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2021-11-30T23:46:05+0000
Creation Date: 2005-06-16T07:00:00+0000
Registrar Registration Expiration Date: 2023-01-01T08:00:00+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895770
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registrant Organization: Google LLC
Registrant State/Province: CA
Registrant Country: US
Registrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/goo.gl
Admin Organization: Google LLC
Admin State/Province: CA
Admin Country: US
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/goo.gl
Tech Organization: Google LLC
Tech State/Province: CA
Tech Country: US
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/goo.gl
Name Server: ns2.google.com
Name Server: ns4.google.com
Name Server: ns1.google.com
Name Server: ns3.google.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-11-07T16:27:20+0000 <<<

For more information on WHOIS status codes, please visit:
https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant, Administrative, or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
https://domains.markmonitor.com/whois

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to whoisrequest@markmonitor.com
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
(1) allow, enable, or otherwise support the transmission by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
(2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

MarkMonitor reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220
--

Nameservers

Name IP Address
ns1.google.com 216.239.32.10
ns2.google.com 216.239.34.10
ns3.google.com 216.239.36.10
ns4.google.com 216.239.38.10
Related

Subdomains

Domain Subdomain
photo

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$4,302 USD 2/5
0/5
0/5
0/5

Sites hosted on the same IP address