In.gr in.gr | Όλες οι ειδήσεις - Ολοκληρωμένη κάλυψη ειδήσεων
Oλες οι βασικές ειδήσεις της ημέρας. Άμεση ενημέρωση για πολιτικά, κοινωνικά, οικονομικά, αθλητικά, τεχνολογικά και άλλα θέματα στο In.gr.
in.gr Desktop Performance
38/100
These metrics represent real-world Chrome users experience viewing in.gr web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
First Input Delay
First Contentful Paint
Cumulative Layout Shift
Largest Contentful Paint
Metrics
Speed Index6/100 4.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint23/100 3.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Total Blocking Time31/100 490 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift43/100 0.284
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Time to Interactive56/100 4.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint89/100 1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Should Fix (18)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript
Potential savings of 462 KiB
770 ms
Reduce initial server response time
Root document took 1,080 ms
480 ms
Avoid multiple page redirects
Potential savings of 380 ms
380 ms
Serve images in next-gen formats
Potential savings of 201 KiB
360 ms
Properly size images
Potential savings of 301 KiB
320 ms
Eliminate render-blocking resources
Potential savings of 80 ms
80 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid `document.write()`
Ensure text remains visible during webfont load
Serve static assets with an efficient cache policy
15 resources found
Avoid an excessive DOM size
1,914 elements
Minimize main-thread work
5.6 s
Reduce JavaScript execution time
2.6 s
Avoids enormous network payloads
Total size was 2,652 KiB
Avoid large layout shifts
5 elements found
Avoid chaining critical requests
20 chains found
Avoid long main-thread tasks
13 long tasks found
Largest Contentful Paint element
1 element found
Keep request counts low and transfer sizes small
160 requests • 2,652 KiB
Passed Audits (11)
Preconnect to required origins
Uses passive listeners to improve scrolling performance
Minimize third-party usage
Third-party code blocked the main thread for 40 ms
Efficiently encode images
Potential savings of 7 KiB
Enable text compression
Potential savings of 2 KiB
Remove unused CSS
Potential savings of 34 KiB
Preload key requests
Defer offscreen images
Potential savings of 306 KiB
Use video formats for animated content
Minify JavaScript
Potential savings of 7 KiB
Minify CSS
Potential savings of 3 KiB
in.gr Desktop SEO
83/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (2)
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Passed Audits (10)
Page has successful HTTP status code
robots.txt is valid
Document has a valid `hreflang`
Document avoids plugins
Page isn’t blocked from indexing
Links have descriptive text
Document has a meta description
Document has a `<title>` element
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document has a valid `rel=canonical`
in.gr Desktop Best Practices
69/100
These checks highlight opportunities to improve the overall code health of in.gr page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
General
Browser errors were logged to the console
Trust and Safety
Does not use HTTPS
2 insecure requests found
Links to cross-origin destinations are unsafe
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Passed Audits (10)
Displays images with correct aspect ratio
Avoids Application Cache
Detected JavaScript libraries
Allows users to paste into password fields
Page has the HTML doctype
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Avoids deprecated APIs
Serves images with appropriate resolution
Properly defines charset
in.gr Desktop Progressive Web App
22/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (9)
PWA Optimized
Is not configured for a custom splash screen
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Installable
Does not use HTTPS
2 insecure requests found
Web app manifest does not meet the installability requirements
Does not register a service worker that controls page and `start_url`
Fast and reliable
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 20.3 s
Passed Audits (4)
Redirects HTTP traffic to HTTPS
Provides a valid `apple-touch-icon`
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Contains some content when JavaScript is not available
in.gr Desktop Accessibility
40/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (9)
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.
Image elements do not have `[alt]` attributes
Links do not have a discernible name
`<frame>` or `<iframe>` elements do not have a title
Form elements do not have associated labels
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
The document uses `<meta http-equiv="refresh">`
Passed Audits (12)
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-hidden="true"]` elements do not contain focusable descendents
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
Heading elements appear in a sequentially-descending order
`[lang]` attributes have a valid value
`<html>` element has a valid value for its `[lang]` attribute
The page contains a heading, skip link, or landmark region
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
`[id]` attributes on active, focusable elements are unique
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
Desktop Speed
57/100
These checks analyze the performance of in.gr on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (8)
Enable compression
Minify JavaScript
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Avoid landing page redirects
Leverage browser caching
Optimize images
Minify CSS
Minify HTML
Passed Audits (2)
Reduce server response time
Prioritize visible content
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
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