IN.GR in.gr | Όλες οι ειδήσεις - Ολοκληρωμένη κάλυψη ειδήσεων


in.gr website information.

in.gr website servers are located in Greece and are responding from following IP address 194.63.247.154. Check the full list of most visited websites located in Greece.

in.gr domain name is registered by .GR top-level domain registry. See the other sites registred in .GR domain zone.

Following name servers are specified for in.gr domain:

  • ns.dolnet.gr
  • ns.in.gr
  • ns1.in.gr

and probably website in.gr is hosted by dolnet.gr web hosting company. Check the complete list of other most popular websites hosted by dolnet.gr hosting company.

According to Alexa traffic rank the highest website in.gr position was 355 (in the world). The lowest Alexa rank position was 11660. Now website in.gr ranked in Alexa database as number 477 (in the world).

Website in.gr Desktop speed measurement score (55/100) is better than the results of 26.24% of other sites shows that the page desktop performance can be improved.

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

Mobile speed measurement score of in.gr (58/100) is better than the results of 49.62% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Sep-23-2019 477-48
Sep-22-2019 42936
Sep-21-2019 465-5
Sep-20-2019 46066
Sep-19-2019 526-20
Sep-18-2019 50684
Sep-17-2019 590-55

Advertisement

in.gr Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.


in.gr whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


in.gr domain is not supported

in.gr server information

Servers Location

in.gr desktop page speed rank

Last tested: 2019-05-21


Desktop Speed Bad
55/100

in.gr Desktop Speed Test Quick Summary


priority - 56 Optimize images

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

Optimize the following images to reduce their size by 544.4KiB (57% reduction).

Compressing https://www.in.gr/wp-content/uploads/2019/05/21130740.jpg could save 149.5KiB (75% reduction).
Compressing https://www.in.gr/wp-content/themes/ingr/common/im…oges/BANNEREKLOGES.jpg could save 114.2KiB (77% reduction).
Compressing https://www.in.gr/wp-content/themes/ingr/common/im…KLOGESBANNERMOBILE.jpg could save 114.2KiB (78% reduction).
Compressing https://www.in.gr/wp-content/themes/ingr/common/imgs/default/ingrlogo.png could save 53KiB (91% reduction).
Compressing and resizing https://www.in.gr/wp-content/uploads/2018/11/EYAGGELATOS-XRISTOFOROS-BW.png could save 28.9KiB (81% reduction).
Compressing and resizing https://www.in.gr/wp-content/uploads/2018/04/MANTELAS-GIORGOS-BW.png could save 26.2KiB (79% reduction).
Compressing https://www.in.gr/wp-content/uploads/2018/04/KANELLHS-ILIAS.png could save 9.9KiB (23% reduction).
Compressing https://www.in.gr/wp-content/uploads/2018/04/GALANHS-BW.png could save 9.5KiB (22% reduction).
Compressing https://www.in.gr/wp-content/uploads/2018/06/xaralampopoulos.png could save 7.7KiB (26% reduction).
Compressing https://www.in.gr/wp-content/uploads/2018/04/DELLHS-BW.png could save 7.6KiB (19% reduction).
Compressing https://www.in.gr/wp-content/uploads/2018/04/PRETENTERHS-BW.png could save 6.3KiB (16% reduction).
Compressing https://www.in.gr/wp-content/uploads/2018/04/FALIDA-BW.png could save 5.5KiB (15% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/01/petrosMakris.png could save 4.2KiB (15% reduction).
Compressing https://www.in.gr/wp-content/uploads/2018/04/BEKOS-path.png could save 3.5KiB (14% reduction).
Compressing and resizing https://www.in.gr/wp-content/themes/ingr/common/imgs/teliacogrlogo-min.png could save 497B (25% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/BBB3A…EAB100782C2-150x77.jpg could save 426B (15% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/1-287-143x85.jpg could save 395B (16% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/gurria2-106x85.jpg could save 386B (12% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/paint-127x85.jpg could save 382B (12% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/00_00…558440695-1-127x85.jpg could save 376B (14% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/%CE%94%CE%A1%CE%91-127x85.jpg could save 372B (14% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/ddsdf-127x85.jpg could save 370B (12% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/xristofias-1-117x85.jpg could save 370B (13% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/kretsos3-128x85.jpg could save 368B (13% reduction).
Compressing https://www.in.gr/wp-content/uploads/2019/05/%CE%9…CE%A4%CE%A3-127x85.jpg could save 363B (13% reduction).

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

Your page has 8 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

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

Remove render-blocking JavaScript:

https://www.in.gr/wp-includes/js/jquery/jquery.js
https://www.alteregomedia.org/files/js/keywords.js
https://www.in.gr/wp-content/cache/autoptimize/js/…ef67032516d65db2016.js
https://vjs.zencdn.net/5.3/video.min.js
https://imasdk.googleapis.com/js/sdkloader/ima3.js
https://cdnjs.cloudflare.com/ajax/libs/videojs-con…2.5/videojs.ads.min.js
https://www.alteregomedia.org/files/js/videojs.ima.js?v=3
https://www.alteregomedia.org/files/js/inread.js?v=5

Optimize CSS Delivery of the following:

https://www.in.gr/wp-content/cache/autoptimize/css…bc93165c04e4daf2d4.css
https://fonts.googleapis.com/css?family=Roboto:300…700&subset=greek,greek
https://cdnjs.cloudflare.com/ajax/libs/videojs-con…/4.2.5/videojs.ads.css
https://vjs.zencdn.net/5.3/video-js.min.css
https://www.google.com/cse/static/element/5d7bf4891789cfae/default+el.css
https://www.google.com/cse/static/style/look/v3/minimalist.css

priority - 7 Avoid landing page redirects

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

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

http://in.gr/
http://www.in.gr/
https://www.in.gr/

priority - 4 Leverage browser caching

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

Leverage browser caching for the following cacheable resources:

https://imasdk.googleapis.com/js/sdkloader/ima3.js (15 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-22217344-1 (15 minutes)
https://connect.facebook.net/el_GR/sdk.js (20 minutes)
https://www.google.com/cse/static/style/look/v3/minimalist.css (50 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://www.googletagservices.com/activeview/js/cu…ner.js?cache=r20110914 (50 minutes)
https://cse.google.com/adsense/search/async-ads.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 4 Prioritize visible content

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

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

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

priority - 1 Minify 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 6KiB (45% reduction).

Minifying https://www.alteregomedia.org/files/js/videojs.ima.js?v=3 could save 4.8KiB (49% reduction) after compression.
Minifying https://connect.facebook.net/el_GR/sdk.js could save 671B (39% reduction) after compression.
Minifying https://www.alteregomedia.org/files/js/inread.js?v=5 could save 527B (31% reduction) after compression.

priority - 0 Minify 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 4.6KiB (33% reduction).

Minifying https://www.google.com/cse/static/element/5d7bf4891789cfae/default+el.css could save 3.8KiB (40% reduction) after compression.
Minifying https://www.google.com/cse/static/style/look/v3/minimalist.css could save 648B (21% reduction) after compression.
Minifying https://epimenidis.in.gr/widgets/css/format.css?v=30102018 could save 142B (12% reduction) after compression.

priority - 0 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 365B (43% reduction).

Compressing https://www.youtube.com/iframe_api could save 365B (43% reduction).

in.gr Desktop Resources

Total Resources158
Number of Hosts38
Static Resources29
JavaScript Resources40
CSS Resources9

in.gr Desktop Resource Breakdown

in.gr mobile page speed rank

Last tested: 2017-05-22


Mobile Speed Bad
58/100

in.gr Mobile Speed Test Quick Summary


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

Your page has 3 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

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

Remove render-blocking JavaScript:

http://mobile.in.gr/js/modernizr-custom.js
https://static.adman.gr/adman.js
http://mobile.in.gr/js/bundle.js?56dbcfd5326a8bac2e31

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Noto+Sans:400,700&subset=greek
http://mobile.in.gr/css/main.css?56dbcfd5326a8bac2e31

priority - 26 Avoid landing page redirects

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

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

http://in.gr/
http://www.in.gr/
http://mobile.in.gr/

priority - 8 Prioritize visible content

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

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

Only about 6% of the final above-the-fold content could be rendered with the full HTML response.

priority - 2 Leverage browser caching

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

Leverage browser caching for the following cacheable resources:

http://mobilefeed.in.gr/home/GetArticlesForHomePage (expiration not specified)
https://static.adman.gr/adman.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 1 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 14KiB (61% reduction).

Compressing http://mobile.in.gr/img/logo.svg could save 7.4KiB (62% reduction).
Compressing http://mobile.in.gr/img/sortdate-blue.svg could save 2.6KiB (66% reduction).
Compressing http://mobile.in.gr/img/refresh.svg could save 1.8KiB (56% reduction).
Compressing http://mobile.in.gr/img/contrast.svg could save 1.1KiB (66% reduction).
Compressing http://mobile.in.gr/img/right-white.svg could save 554B (47% reduction).
Compressing http://mobile.in.gr/img/left-white.svg could save 548B (48% reduction).

priority - 0 Optimize images

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

Optimize the following images to reduce their size by 1.2KiB (12% reduction).

Compressing http://www.in.gr/28476700_1__1_.limghandler.jpg?i=…cyMTUmY3I9dHJ1ZSZhdD00 could save 1.2KiB (12% reduction).

in.gr Mobile Resources

Total Resources81
Number of Hosts9
Static Resources4
JavaScript Resources5
CSS Resources2

in.gr Mobile Resource Breakdown

in.gr mobile page usability

Last tested: 2017-05-22


Mobile Usability Good
96/100

in.gr Mobile Usability Test Quick Summary


priority - 3 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <div class="slick-list draggable">Τσακαλώτος: Όλ…Οικονομία</div> is close to 1 other tap targets.

The tap target <div>Τσακαλώτος: Όλ…Οικονομία</div> and 2 others are close to other tap targets.

The tap target <div>Τσακαλώτος: Όλ…Οικονομία</div> and 2 others are close to other tap targets.

The tap target <li id="slick-slide00" class="slick-active">1</li> and 2 others are close to other tap targets.
The tap target <li id="slick-slide00" class="slick-active">1</li> and 1 others are close to other tap targets.
The tap target <button type="button">1</button> and 2 others are close to other tap targets.
The tap target <li id="slick-slide01">2</li> and 3 others are close to other tap targets.
The tap target <a href="/GoToDesktop.a…p://www.in.gr/">Μεταφορά στο www.in.gr</a> is close to 10 other tap targets.

in.gr Mobile Resources

Total Resources81
Number of Hosts9
Static Resources4
JavaScript Resources5
CSS Resources2

in.gr Mobile Resource Breakdown

in.gr similar domains

Similar domains:
www.in.com
www.in.net
www.in.org
www.in.info
www.in.biz
www.in.us
www.in.mobi
www.n.gr
www.in.gr
www.un.gr
www.iun.gr
www.uin.gr
www.jn.gr
www.ijn.gr
www.jin.gr
www.kn.gr
www.ikn.gr
www.kin.gr
www.on.gr
www.ion.gr
www.oin.gr
www.i.gr
www.ib.gr
www.inb.gr
www.ibn.gr
www.ih.gr
www.inh.gr
www.ihn.gr
www.ij.gr
www.inj.gr
www.im.gr
www.inm.gr
www.imn.gr

in.gr Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


in.gr TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.