In.gr in.gr | Όλες οι ειδήσεις - Ολοκληρωμένη κάλυψη ειδήσεων
Oλες οι βασικές ειδήσεις της ημέρας. Άμεση ενημέρωση για πολιτικά, κοινωνικά, οικονομικά, αθλητικά, τεχνολογικά και άλλα θέματα στο In.gr.
in.gr Mobile Performance
16/100
These metrics represent real-world Chrome users experience viewing in.gr on mobile devices. 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
Largest Contentful Paint
Cumulative Layout Shift
First Input Delay
First Contentful Paint
Metrics
Largest Contentful Paint0/100 16.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Speed Index1/100 14.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time3/100 1,810 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Time to Interactive3/100 18.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint65/100 3.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Cumulative Layout Shift89/100 0.104
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (23)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript
Potential savings of 422 KiB
2,880 ms
Avoid multiple page redirects
Potential savings of 1,260 ms
1,260 ms
Use video formats for animated content
Potential savings of 118 KiB
1,220 ms
Defer offscreen images
Potential savings of 306 KiB
660 ms
Reduce initial server response time
Root document took 1,240 ms
643 ms
Serve images in next-gen formats
Potential savings of 157 KiB
480 ms
Eliminate render-blocking resources
Potential savings of 450 ms
450 ms
Remove unused CSS
Potential savings of 31 KiB
300 ms
Minify JavaScript
Potential savings of 7 KiB
120 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Reduce the impact of third-party code
Third-party code blocked the main thread for 700 ms
Avoid `document.write()`
Minimize main-thread work
11.8 s
Serve static assets with an efficient cache policy
15 resources found
Avoid an excessive DOM size
1,867 elements
Reduce JavaScript execution time
5.9 s
Avoids enormous network payloads
Total size was 2,419 KiB
Keep request counts low and transfer sizes small
133 requests • 2,419 KiB
Avoid long main-thread tasks
20 long tasks found
Largest Contentful Paint element
1 element found
User Timing marks and measures
8 user timings
Avoid large layout shifts
5 elements found
Avoid chaining critical requests
21 chains found
Passed Audits (7)
Enable text compression
Potential savings of 2 KiB
Efficiently encode images
Preconnect to required origins
Properly size images
Minify CSS
Potential savings of 3 KiB
Preload key requests
Uses passive listeners to improve scrolling performance
in.gr Mobile SEO
84/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 (3)
Crawling and Indexing
To appear in search results, crawlers need access to your app.
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.
Tap targets are not sized appropriately
82% appropriately sized tap targets
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
Passed Audits (11)
Page isn’t blocked from indexing
robots.txt is valid
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document avoids plugins
Document has a `<title>` element
Links have descriptive text
Document has a valid `hreflang`
Page has successful HTTP status code
Document has a valid `rel=canonical`
Document has a meta description
Document uses legible font sizes
99.41% legible text
in.gr Mobile Best Practices
69/100
These checks highlight opportunities to improve the overall code health of in.gr mobile 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
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Does not use HTTPS
2 insecure requests found
Links to cross-origin destinations are unsafe
Passed Audits (10)
Allows users to paste into password fields
Properly defines charset
Detected JavaScript libraries
Displays images with correct aspect ratio
Avoids deprecated APIs
Avoids requesting the geolocation permission on page load
Avoids Application Cache
Serves images with appropriate resolution
Page has the HTML doctype
Avoids requesting the notification permission on page load
in.gr Mobile Progressive Web App
25/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
Does not set a theme color for the address bar.
Is not configured for a custom splash screen
Manifest doesn't have a maskable icon
Installable
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
2 insecure requests found
Web app manifest does not meet the installability requirements
Fast and reliable
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive at 18.7 s
Passed Audits (5)
Content is sized correctly for the viewport
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Contains some content when JavaScript is not available
Redirects HTTP traffic to HTTPS
Provides a valid `apple-touch-icon`
in.gr Mobile Accessibility
41/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 (8)
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">`
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.
`<frame>` or `<iframe>` elements do not have a title
Image elements do not have `[alt]` attributes
Links do not have a discernible name
Form elements do not have associated labels
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (10)
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Heading elements appear in a sequentially-descending order
`[aria-hidden="true"]` is not present on the document `<body>`
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
`[aria-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
The page contains a heading, skip link, or landmark region
`[id]` attributes on active, focusable elements are unique
`[lang]` attributes have a valid value
Mobile Usability
96/100
These checks validate how easily a visitor can use in.gr on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Should Fix (1)
Size tap targets appropriately
Passed Audits (4)
Avoid plugins
Configure the viewport
Size content to viewport
Use legible font sizes
Mobile Speed
58/100
These checks analyze the performance of in.gr on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (6)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Avoid landing page redirects
Prioritize visible content
Leverage browser caching
Enable compression
Optimize images
Passed Audits (4)
Reduce server response time
Minify CSS
Minify HTML
Minify JavaScript
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