GILLY.BERLIN @GillyBerlin – Enthält Spuren von Katzen

gilly.berlin Website Information

Daily Unique Visits: 1,033

Daily Page Views: 2,066

Income Per Day: $6

Estimated Value: $1,440

gilly.berlin is registered under .BERLIN top-level domain. Please check other sites in .BERLIN zone.

No name server records were found.

and is probably hosted by Hetzner Online GmbH. See the full list of other websites hosted by Hetzner Online GmbH.

The highest website gilly.berlin position in Alexa rank database was 22706 and the lowest rank position was 999675. Current position of gilly.berlin in Alexa rank database is 693994.

Desktop speed score of gilly.berlin (72/100) is better than the results of 54.39% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of gilly.berlin (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.

Mobile speed score of gilly.berlin (74/100) is better than the results of 83.2% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

gilly.berlin Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


gilly.berlin whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


Domain Name: gilly.berlin
Registry Domain ID: D0000186759-BERLIN
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL: http://www.key-systems.net/tld/berlin
Updated Date: 2019-02-19T17:00:11Z
Creation Date: 2014-06-17T07:48:14Z
Registry Expiry Date: 2022-06-17T07:48:14Z
Registrar: Key-Systems LLC
Registrar IANA ID: 1345
Registrar Abuse Contact Email: info@key-systems.net
Registrar Abuse Contact Phone: +49.68949396850
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ns.second-ns.com
Name Server: ns1.your-server.de
Name Server: ns3.second-ns.de
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of Whois database: 2022-05-23T22:25:46Z

gilly.berlin server information

Servers Location

gilly.berlin desktop page speed rank

Last tested: 2019-02-04


Desktop Speed Medium
72/100

gilly.berlin Desktop Speed Test Quick Summary


priority - 25Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 243.7KiB (46% reduction).

Compressing and resizing https://gilly.berlin/wp-content/uploads/2018/12/GYMKHANA-TEN.jpg could save 82.3KiB (79% reduction).
Compressing https://gilly.berlin/wp-content/uploads/2018/12/Shenzhen-1024x576.jpg could save 64.4KiB (43% reduction).
Compressing and resizing https://gilly.berlin/wp-content/uploads/2018/12/Geschichte-des-Kaeses-1.jpg could save 62.7KiB (82% reduction).
Compressing https://gilly.berlin/wp-content/uploads/2019/01/RobotWorks-1024x576.jpg could save 13.7KiB (12% reduction).
Compressing https://gilly.berlin/wp-content/uploads/2019/01/Le-Bon-Berger-1024x576.jpg could save 11.1KiB (19% reduction).
Compressing https://gilly.berlin/wp-content/uploads/2019/01/Einsakeit-1024x576.jpg could save 9.5KiB (36% reduction).

priority - 5Leverage browser caching

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

Leverage browser caching for the following cacheable resources:

https://gilly.berlin/wp-content/plugins/a3-lazy-lo…xt.extend.js?ver=1.9.2 (2 days)
https://gilly.berlin/wp-content/plugins/a3-lazy-lo…extra.min.js?ver=1.9.2 (2 days)
https://gilly.berlin/wp-content/plugins/a3-lazy-lo…rcset.min.js?ver=1.9.2 (2 days)
https://gilly.berlin/wp-content/plugins/baguettebo…js/dist/baguettebox.js (2 days)
https://gilly.berlin/wp-content/plugins/wp-gdpr-co…ront.js?ver=1548057290 (2 days)
https://gilly.berlin/wp-content/plugins/wp-gdpr-co….min.js?ver=1548057291 (2 days)
https://gilly.berlin/wp-content/themes/pukeko/assets/images/sprite.svg (2 days)
https://gilly.berlin/wp-content/themes/pukeko/assets/js/custom.js?ver=1.0 (2 days)
https://gilly.berlin/wp-content/themes/pukeko/asse…/navigation.js?ver=1.0 (2 days)
https://gilly.berlin/wp-content/themes/pukeko/asse…k-focus-fix.js?ver=1.0 (2 days)
https://gilly.berlin/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1 (2 days)
https://gilly.berlin/wp-includes/js/jquery/jquery.js?ver=1.12.4 (2 days)
https://gilly.berlin/wp-includes/js/wp-embed.min.js?ver=5.0.3 (2 days)
https://gilly.berlin/wp-includes/js/wp-emoji-release.min.js?ver=5.0.3 (2 days)

priority - 5Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 46.6KiB (74% reduction).

Minifying https://gilly.berlin/wp-content/themes/pukeko/style.css?ver=5.0.3 could save 46.4KiB (73% reduction) after compression.
Minifying https://gilly.berlin/wp-content/themes/pukeko-child/style.css?ver=1.0.0 could save 276B (93% reduction) after compression.

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

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

Optimize CSS Delivery of the following:

https://gilly.berlin/wp-content/plugins/baguettebo…uettebox.css?ver=5.0.3

priority - 1Reduce server response time

In our test, your server responded in 0.27 seconds.

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.8KiB (20% reduction).

Minifying https://gilly.berlin/wp-content/plugins/wp-gdpr-co…ront.js?ver=1548057290 could save 503B (20% reduction) after compression.
Minifying https://gilly.berlin/wp-content/plugins/baguettebo…js/dist/baguettebox.js could save 486B (12% reduction) after compression.
Minifying https://gilly.berlin/wp-content/themes/pukeko/asse…/navigation.js?ver=1.0 could save 359B (32% reduction) after compression.
Minifying https://gilly.berlin/wp-content/themes/pukeko/assets/js/custom.js?ver=1.0 could save 328B (42% reduction) after compression.
Minifying https://gilly.berlin/wp-content/themes/pukeko/asse…k-focus-fix.js?ver=1.0 could save 138B (34% reduction) after compression.

gilly.berlin Desktop Resource Breakdown

Total Resources35
Number of Hosts4
Static Resources29
JavaScript Resources13
CSS Resources9

gilly.berlin mobile page speed rank

Last tested: 2019-02-04


Mobile Speed Medium
74/100

gilly.berlin Mobile Speed Test Quick Summary


priority - 12Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 118.4KiB (27% reduction).

Compressing https://gilly.berlin/wp-content/uploads/2018/12/Shenzhen-1024x576.jpg could save 64.4KiB (43% reduction).
Compressing https://gilly.berlin/wp-content/uploads/2019/01/RobotWorks-1024x576.jpg could save 13.7KiB (12% reduction).
Compressing https://gilly.berlin/wp-content/uploads/2019/01/Le-Bon-Berger-1024x576.jpg could save 11.1KiB (19% reduction).
Compressing https://gilly.berlin/wp-content/uploads/2018/12/GYMKHANA-TEN-1024x576.jpg could save 10KiB (19% reduction).
Compressing https://gilly.berlin/wp-content/uploads/2018/12/Ge…-Kaeses-1-1024x576.jpg could save 9.7KiB (27% reduction).
Compressing https://gilly.berlin/wp-content/uploads/2019/01/Einsakeit-1024x576.jpg could save 9.5KiB (36% reduction).

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

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

Optimize CSS Delivery of the following:

https://gilly.berlin/wp-content/plugins/baguettebo…uettebox.css?ver=5.0.3

priority - 8Leverage browser caching

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

Leverage browser caching for the following cacheable resources:

https://gilly.berlin/wp-content/plugins/a3-lazy-lo…xt.extend.js?ver=1.9.2 (2 days)
https://gilly.berlin/wp-content/plugins/a3-lazy-lo…extra.min.js?ver=1.9.2 (2 days)
https://gilly.berlin/wp-content/plugins/a3-lazy-lo…rcset.min.js?ver=1.9.2 (2 days)
https://gilly.berlin/wp-content/plugins/baguettebo…js/dist/baguettebox.js (2 days)
https://gilly.berlin/wp-content/plugins/wp-gdpr-co…ront.js?ver=1548057290 (2 days)
https://gilly.berlin/wp-content/plugins/wp-gdpr-co….min.js?ver=1548057291 (2 days)
https://gilly.berlin/wp-content/themes/pukeko/assets/images/sprite.svg (2 days)
https://gilly.berlin/wp-content/themes/pukeko/assets/js/custom.js?ver=1.0 (2 days)
https://gilly.berlin/wp-content/themes/pukeko/asse…/navigation.js?ver=1.0 (2 days)
https://gilly.berlin/wp-content/themes/pukeko/asse…k-focus-fix.js?ver=1.0 (2 days)
https://gilly.berlin/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1 (2 days)
https://gilly.berlin/wp-includes/js/jquery/jquery.js?ver=1.12.4 (2 days)
https://gilly.berlin/wp-includes/js/wp-embed.min.js?ver=5.0.3 (2 days)
https://gilly.berlin/wp-includes/js/wp-emoji-release.min.js?ver=5.0.3 (2 days)

priority - 5Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 46.6KiB (74% reduction).

Minifying https://gilly.berlin/wp-content/themes/pukeko/style.css?ver=5.0.3 could save 46.4KiB (73% reduction) after compression.
Minifying https://gilly.berlin/wp-content/themes/pukeko-child/style.css?ver=1.0.0 could save 276B (93% reduction) after compression.

priority - 1Reduce server response time

In our test, your server responded in 0.27 seconds.

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.8KiB (20% reduction).

Minifying https://gilly.berlin/wp-content/plugins/wp-gdpr-co…ront.js?ver=1548057290 could save 503B (20% reduction) after compression.
Minifying https://gilly.berlin/wp-content/plugins/baguettebo…js/dist/baguettebox.js could save 486B (12% reduction) after compression.
Minifying https://gilly.berlin/wp-content/themes/pukeko/asse…/navigation.js?ver=1.0 could save 359B (32% reduction) after compression.
Minifying https://gilly.berlin/wp-content/themes/pukeko/assets/js/custom.js?ver=1.0 could save 328B (42% reduction) after compression.
Minifying https://gilly.berlin/wp-content/themes/pukeko/asse…k-focus-fix.js?ver=1.0 could save 138B (34% reduction) after compression.

gilly.berlin Mobile Resource Breakdown

Total Resources34
Number of Hosts4
Static Resources29
JavaScript Resources13
CSS Resources9

gilly.berlin mobile page usability

Last tested: 2019-02-04


Mobile Usability Good
100/100

gilly.berlin HTML validation

Warnings

The “banner” role is unnecessary for element “header”.

Line: 2 Column: 4413 - 4486
"...ringen</a><header id="masthead" class="site-header masthead nav-down" role="banner"><div c..."

The “navigation” role is unnecessary for element “nav”.

Line: 2 Column: 5080 - 5147
"...nav-wrap"><nav id="site-navigation" class="main-navigation" role="navigation"><div c..." Line: 5 Column: 151 - 233
"...orm></div><nav id="social-header-nav" class="social-header-nav social-nav" role="navigation"><div c..." Line: 5 Column: 15514 - 15566
"...cle></div><nav class="navigation pagination" role="navigation"><h2 cl..." Line: 5 Column: 17909 - 17966
"...-wrap cf"><nav id="footer-nav" class="footer-nav" role="navigation"><ul id..." Line: 5 Column: 18511 - 18593
".../ul></nav><nav id="social-footer-nav" class="social-footer-nav social-nav" role="navigation"><div c..."

The “main” role is unnecessary for element “main”.

Line: 5 Column: 1817 - 1862
"...ent-area"><main id="main" class="site-main" role="main"><div c..."

The “contentinfo” role is unnecessary for element “footer”.

Line: 5 Column: 16403 - 16463
"...div></div><footer id="colophon" class="site-footer" role="contentinfo"><div c..."

The “complementary” role is unnecessary for element “aside”.

Line: 5 Column: 16492 - 16581
"...-wrap cf"><aside class="footer-widget-wrap widget-area widget-area-default cf" role="complementary"><div i..."

Errors

Attribute “href” not allowed on element “use” at this point.

Line: 2 Column: 5585 - 5643
"...le="img"> <use href="#icon-caret-down" xlink:href="#icon-caret-down"></use>..." Line: 2 Column: 8272 - 8330
"...le="img"> <use href="#icon-caret-down" xlink:href="#icon-caret-down"></use>..." Line: 2 Column: 8862 - 8918
"...le="img"> <use href="#icon-magnifier" xlink:href="#icon-magnifier"></use>..." Line: 5 Column: 572 - 624
"...le="img"> <use href="#icon-twitter" xlink:href="#icon-twitter"></use>..." Line: 5 Column: 908 - 964
"...le="img"> <use href="#icon-instagram" xlink:href="#icon-instagram"></use>..." Line: 5 Column: 1249 - 1303
"...le="img"> <use href="#icon-facebook" xlink:href="#icon-facebook"></use>..." Line: 5 Column: 1594 - 1646
"...le="img"> <use href="#icon-youtube" xlink:href="#icon-youtube"></use>..." Line: 5 Column: 16186 - 16246
"...le="img"> <use href="#icon-arrow-right" xlink:href="#icon-arrow-right"></use>..." Line: 5 Column: 18913 - 18965
"...le="img"> <use href="#icon-twitter" xlink:href="#icon-twitter"></use>..." Line: 5 Column: 19228 - 19284
"...le="img"> <use href="#icon-instagram" xlink:href="#icon-instagram"></use>..." Line: 5 Column: 19548 - 19602
"...le="img"> <use href="#icon-facebook" xlink:href="#icon-facebook"></use>..." Line: 5 Column: 19872 - 19924
"...le="img"> <use href="#icon-youtube" xlink:href="#icon-youtube"></use>..."

The “aria-controls” attribute must point to an element in the same document.

Line: 2 Column: 4714 - 4810
"...ntainer"> <button id="hamburger" class="menu-toggle" aria-controls="main-navigation" aria-expanded="false"> <span..."

The “itemprop” attribute was specified, but the element is not a property of any item.

Line: 2 Column: 3694 - 3739
"...9360185"/><meta itemprop="name" content="@GillyBerlin"/><meta ..." Line: 2 Column: 3740 - 3789
"...yBerlin"/><meta itemprop="headline" content="@GillyBerlin"/><meta ..." Line: 2 Column: 3790 - 3855
"...yBerlin"/><meta itemprop="description" content="Enthält Spuren von Katzen"/><meta ..."

gilly.berlin similar domains

Similar domains:
www.gilly.com
www.gilly.net
www.gilly.org
www.gilly.info
www.gilly.biz
www.gilly.us
www.gilly.mobi
www.illy.berlin
www.gilly.berlin
www.filly.berlin
www.gfilly.berlin
www.fgilly.berlin
www.villy.berlin
www.gvilly.berlin
www.vgilly.berlin
www.tilly.berlin
www.gtilly.berlin
www.tgilly.berlin
www.billy.berlin
www.gbilly.berlin
www.bgilly.berlin
www.yilly.berlin
www.gyilly.berlin
www.ygilly.berlin
www.hilly.berlin
www.ghilly.berlin
www.hgilly.berlin
www.glly.berlin
www.gully.berlin
www.giully.berlin
www.guilly.berlin
www.gjlly.berlin
www.gijlly.berlin
www.gjilly.berlin
www.gklly.berlin
www.giklly.berlin
www.gkilly.berlin
www.golly.berlin
www.giolly.berlin
www.goilly.berlin
www.gily.berlin
www.giply.berlin
www.gilply.berlin
www.giplly.berlin
www.gioly.berlin
www.giloly.berlin
www.gikly.berlin
www.gilkly.berlin
www.gilpy.berlin
www.gillpy.berlin
www.giloy.berlin
www.gilloy.berlin
www.gilky.berlin
www.gillky.berlin
www.gill.berlin
www.gillt.berlin
www.gillyt.berlin
www.gillty.berlin
www.gillg.berlin
www.gillyg.berlin
www.gillgy.berlin
www.gillh.berlin
www.gillyh.berlin
www.gillhy.berlin
www.gillu.berlin
www.gillyu.berlin
www.gilluy.berlin

gilly.berlin Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


gilly.berlin TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.