Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

in.gr

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

Page Load Speed

8.4 sec in total

First Response

473 ms

Resources Loaded

7.4 sec

Page Rendered

501 ms

in.gr screenshot

About Website

Visit in.gr now to see the best up-to-date In content for Greece and also check out these interesting facts you probably never knew about in.gr

Oλες οι βασικές ειδήσεις της ημέρας. Άμεση ενημέρωση για πολιτικά, κοινωνικά, οικονομικά, αθλητικά, τεχνολογικά και άλλα θέματα στο In.gr.

Visit in.gr

Key Findings

We analyzed In.gr page load time and found that the first response time was 473 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

in.gr performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value5,790 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

in.gr

473 ms

www.in.gr

528 ms

9882EF142EE88FEF6A81A056ECE099B73.css

787 ms

3DED7AA5A5D3625B22EFFB9EE9857182.js

806 ms

83D2A46B153AC50EE1B90E29B4A58642.js

613 ms

Our browser made a total of 299 requests to load all elements on the main page. We found that 19% of them (58 requests) were addressed to the original In.gr, 36% (107 requests) were made to Static.in.gr and 8% (24 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Static.in.gr.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (51%)

Content Size

5.0 MB

After Optimization

2.4 MB

In fact, the total size of In.gr main page is 5.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 190.3 kB

  • Original 231.2 kB
  • After minification 202.5 kB
  • After compression 40.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 28.7 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 190.3 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 145.1 kB

  • Original 1.7 MB
  • After minification 1.6 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. In images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 1.4 MB

  • Original 2.0 MB
  • After minification 1.8 MB
  • After compression 572.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.4 MB or 71% of the original size.

CSS Optimization

-78%

Potential reduce by 794.0 kB

  • Original 1.0 MB
  • After minification 970.3 kB
  • After compression 227.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. In.gr needs all CSS files to be minified and compressed as it can save up to 794.0 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 106 (38%)

Requests Now

276

After Optimization

170

The browser has sent 276 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

in.gr accessibility score

73

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

in.gr best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

in.gr SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EL

  • Language Claimed

    EL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise In.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it matches the claimed language. Our system also found out that In.gr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of In. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: