Gds.it Quotidiano online del Giornale di Sicilia, notizie e cronaca
Giornale di Sicilia - il sito web del quotidiano che da oltre 150 anni informa con notizie dalla Sicilia e dall'Italia su cronaca, politica, economia,...
gds.it Desktop Performance
71/100
These metrics represent real-world Chrome users experience viewing gds.it 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
Cumulative Layout Shift
First Input Delay
First Contentful Paint
Largest Contentful Paint
Metrics
Largest Contentful Paint50/100 2.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Speed Index56/100 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive63/100 3.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint87/100 1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Total Blocking Time92/100 140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift100/100 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (16)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript
Potential savings of 284 KiB
400 ms
Eliminate render-blocking resources
Potential savings of 340 ms
339 ms
Serve images in next-gen formats
Potential savings of 252 KiB
200 ms
Reduce initial server response time
Root document took 760 ms
165 ms
Defer offscreen images
Potential savings of 86 KiB
80 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Ensure text remains visible during webfont load
Avoid an excessive DOM size
2,572 elements
Minimize main-thread work
2.5 s
JavaScript execution time
1.3 s
Uses efficient cache policy on static assets
8 resources found
Avoid long main-thread tasks
9 long tasks found
Avoid chaining critical requests
16 chains found
Avoid large layout shifts
1 element found
Largest Contentful Paint element
1 element found
Keep request counts low and transfer sizes small
135 requests • 1,928 KiB
Passed Audits (13)
Minimize third-party usage
Third-party code blocked the main thread for 160 ms
Enable text compression
Minify JavaScript
Properly size images
Efficiently encode images
Preconnect to required origins
Use video formats for animated content
Minify CSS
Remove unused CSS
Potential savings of 63 KiB
Preload key requests
Avoids enormous network payloads
Total size was 1,928 KiB
Avoid multiple page redirects
Potential savings of 190 ms
Avoids `document.write()`
gds.it 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)
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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Passed Audits (10)
Page has successful HTTP status code
Document avoids plugins
Document has a `<title>` element
Document has a valid `rel=canonical`
Document has a valid `hreflang`
Page isn’t blocked from indexing
Links have descriptive text
Image elements have `[alt]` attributes
robots.txt is valid
Document has a meta description
gds.it Desktop Best Practices
77/100
These checks highlight opportunities to improve the overall code health of gds.it 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 (3)
Trust and Safety
Links to cross-origin destinations are unsafe
Does not use HTTPS
1 insecure request found
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Passed Audits (11)
No browser errors logged to the console
Avoids Application Cache
Page has the HTML doctype
Avoids deprecated APIs
Avoids requesting the geolocation permission on page load
Detected JavaScript libraries
Avoids requesting the notification permission on page load
Serves images with appropriate resolution
Allows users to paste into password fields
Properly defines charset
Displays images with correct aspect ratio
gds.it Desktop Progressive Web App
11/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 (11)
PWA Optimized
Does not set a theme color for the address bar.
Manifest doesn't have a maskable icon
Is not configured for a custom splash screen
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Does not provide a valid `apple-touch-icon`
Fast and reliable
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 17.3 s
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
Installable
Web app manifest does not meet the installability requirements
Does not use HTTPS
1 insecure request found
Does not register a service worker that controls page and `start_url`
Passed Audits (2)
Contains some content when JavaScript is not available
Redirects HTTP traffic to HTTPS
gds.it Desktop Accessibility
81/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 (6)
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Form elements do not have associated labels
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
The document uses `<meta http-equiv="refresh">`
Passed Audits (19)
`[id]` attributes on active, focusable elements are unique
`[role]`s are contained by their required parent element
No element has a `[tabindex]` value greater than 0
`[aria-*]` attributes match their roles
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
Document has a `<title>` element
`<html>` element has a valid value for its `[lang]` attribute
`[aria-*]` attributes have valid values
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Image elements have `[alt]` attributes
The page contains a heading, skip link, or landmark region
ARIA IDs are unique
`[role]`s have all required `[aria-*]` attributes
`<html>` element has a `[lang]` attribute
`[role]` values are valid
Desktop Speed
77/100
These checks analyze the performance of gds.it 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 (5)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Enable compression
Leverage browser caching
Optimize images
Minify HTML
Passed Audits (5)
Avoid landing page redirects
Reduce server response time
Minify CSS
Minify JavaScript
Prioritize visible content
www.gds.com
www.gds.net
www.gds.org
www.gds.info
www.gds.biz
www.gds.us
www.gds.mobi
www.ds.it
www.gds.it
www.fds.it
www.gfds.it
www.fgds.it
www.vds.it
www.gvds.it
www.vgds.it
www.tds.it
www.gtds.it
www.tgds.it
www.bds.it
www.gbds.it
www.bgds.it
www.yds.it
www.gyds.it
www.ygds.it
www.hds.it
www.ghds.it
www.hgds.it
www.gs.it
www.gxs.it
www.gdxs.it
www.gxds.it
www.gss.it
www.gdss.it
www.gsds.it
www.ges.it
www.gdes.it
www.geds.it
www.grs.it
www.gdrs.it
www.grds.it
www.gfs.it
www.gdfs.it
www.gcs.it
www.gdcs.it
www.gcds.it
www.gd.it
www.gdw.it
www.gdsw.it
www.gdws.it
www.gde.it
www.gdse.it
www.gdd.it
www.gdsd.it
www.gdds.it
www.gdz.it
www.gdsz.it
www.gdzs.it
www.gdx.it
www.gdsx.it
www.gda.it
www.gdsa.it
www.gdas.it
www.gds.net
www.gds.org
www.gds.info
www.gds.biz
www.gds.us
www.gds.mobi
www.ds.it
www.gds.it
www.fds.it
www.gfds.it
www.fgds.it
www.vds.it
www.gvds.it
www.vgds.it
www.tds.it
www.gtds.it
www.tgds.it
www.bds.it
www.gbds.it
www.bgds.it
www.yds.it
www.gyds.it
www.ygds.it
www.hds.it
www.ghds.it
www.hgds.it
www.gs.it
www.gxs.it
www.gdxs.it
www.gxds.it
www.gss.it
www.gdss.it
www.gsds.it
www.ges.it
www.gdes.it
www.geds.it
www.grs.it
www.gdrs.it
www.grds.it
www.gfs.it
www.gdfs.it
www.gcs.it
www.gdcs.it
www.gcds.it
www.gd.it
www.gdw.it
www.gdsw.it
www.gdws.it
www.gde.it
www.gdse.it
www.gdd.it
www.gdsd.it
www.gdds.it
www.gdz.it
www.gdsz.it
www.gdzs.it
www.gdx.it
www.gdsx.it
www.gda.it
www.gdsa.it
www.gdas.it