PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Mar 13, 2025, 10:11:19 AM
Discover what your real users are experiencing
No Data
Diagnose performance issues
69
Performance
100
Accessibility
96
Best Practices
100
SEO
69
Performance
100
Accessibility
96
Best Practices
100
SEO
69 FCP+3LCP+5TBT+30CLS+25SI+6 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
3.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
5.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
5.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 13, 2025, 10:11 AM UTC
  • Emulated Moto G Power with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 509 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: Europe
  • Using HeadlessChromium 133.0.6943.141 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Eliminate render-blocking resources Potential savings of 1,920 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
WordPressThere are a number of WordPress plugins that can help you inline critical assets or defer less important resources. Beware that optimizations provided by these plugins may break features of your theme or plugins, so you will likely need to make code changes.
URL
Transfer Size
Potential Savings
boomdigitale.it
1st party
121.9 KiB
2,400 ms
…jquery/jquery.min.js?ver=3.7.1
(www.boomdigitale.it)
30.2 KiB
600 ms
…block-library/style.min.css?ver=6.7.2
(www.boomdigitale.it)
15.3 KiB
150 ms
…css/styles.css?ver=6.0.4
(www.boomdigitale.it)
1.5 KiB
150 ms
…js/masonry.min.js
(www.boomdigitale.it)
7.7 KiB
150 ms
…js/tweenmax.min.js
(www.boomdigitale.it)
39.3 KiB
300 ms
…newsletter/style.css?ver=8.7.1
(www.boomdigitale.it)
1.9 KiB
150 ms
…js/app.js?ver=4.17
(www.boomdigitale.it)
3.5 KiB
150 ms
…css/main.css?ver=6.7.2
(www.boomdigitale.it)
0.8 KiB
150 ms
…js/scrollmagic.js
(www.boomdigitale.it)
6.4 KiB
150 ms
…js/index.js?ver=6.0.4
(www.boomdigitale.it)
4.7 KiB
150 ms
…js/swup.min.js
(www.boomdigitale.it)
5.4 KiB
150 ms
…jquery/jquery-migrate.min.js?ver=3.4.1
(www.boomdigitale.it)
5.3 KiB
150 ms
iubenda
utility
11.8 KiB
930 ms
/autoblocking/3318616.js
(cs.iubenda.com)
11.8 KiB
930 ms
Largest Contentful Paint element 5,470 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
e se trasformassimo la tua idea in un sito web?
<h1>
Phase
% of LCP
Timing
TTFB
11%
600 ms
Load Delay
0%
0 ms
Load Time
0%
0 ms
Render Delay
89%
4,870 ms
Reduce unused CSS Potential savings of 15 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
WordPressConsider reducing, or switching, the number of WordPress plugins loading unused CSS in your page. To identify plugins that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a stylesheet if it is actually used on the page.
URL
Transfer Size
Potential Savings
boomdigitale.it
1st party
14.7 KiB
14.5 KiB
…block-library/style.min.css?ver=6.7.2
(www.boomdigitale.it)
14.7 KiB
14.5 KiB
Reduce unused JavaScript Potential savings of 152 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
WordPressConsider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your page. To identify plugins that are adding extraneous JS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the script. Look out for plugins that have many scripts in the list which have a lot of red in code coverage. A plugin should only enqueue a script if it is actually used on the page.
URL
Transfer Size
Potential Savings
Unattributable
182.3 KiB
91.7 KiB
/gtm.js?id=GTM-PZ7Q74B9
(www.googletagmanager.com)
108.5 KiB
56.5 KiB
/modules.ef5986d….js
(script.hotjar.com)
73.7 KiB
35.2 KiB
iubenda
utility
70.1 KiB
31.0 KiB
…1.76.2/core-it.js
(cdn.iubenda.com)
70.1 KiB
31.0 KiB
boomdigitale.it
1st party
38.7 KiB
29.7 KiB
…js/tweenmax.min.js
(www.boomdigitale.it)
38.7 KiB
29.7 KiB
Remove duplicate modules in JavaScript bundles Potential savings of 1 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Source
Transfer Size
Potential Savings
webpack://trustindex/./web/dev/js/loader/TrustindexCommon.js
0 KiB
/loader.js
(cdn.trustindex.io)
0 KiB
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
0 KiB
Serve static assets with an efficient cache policy 7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
WordPressRead about Browser Caching in WordPress.
URL
Cache TTL
Transfer Size
trustindex.io
85 KiB
…js/cert-translations.js
(cdn.trustindex.io)
None
60 KiB
/loader.js
(cdn.trustindex.io)
None
16 KiB
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
None
5 KiB
…widget-presetted-css/74-default.css
(cdn.trustindex.io)
None
4 KiB
iubenda
utility
14 KiB
/autoblocking/3318616.js
(cs.iubenda.com)
1h
12 KiB
/cs/iubenda_cs.js?ver=3.12.1
(cdn.iubenda.com)
1h
1 KiB
…js/82105649.js
(cs.iubenda.com)
1h
1 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
boomdigitale.it
1st party
0.3 KiB
…js/SwupHeadPlugin.min.js
(www.boomdigitale.it)
0.1 KiB
…js/SwupHeadPlugin.min.js:1:1813
(www.boomdigitale.it)
@babel/plugin-transform-classes
…js/SwupBodyClassPlugin.min.js
(www.boomdigitale.it)
0.1 KiB
…js/SwupBodyClassPlugin.min.js:1:1995
(www.boomdigitale.it)
@babel/plugin-transform-classes
…js/SwupStylesPlugin.min.js
(www.boomdigitale.it)
0.1 KiB
…js/SwupStylesPlugin.min.js:1:1817
(www.boomdigitale.it)
@babel/plugin-transform-classes
…js/SwupScrollPlugin.min.js
(www.boomdigitale.it)
0.1 KiB
…js/SwupScrollPlugin.min.js:1:2011
(www.boomdigitale.it)
@babel/plugin-transform-classes
…js/swup.min.js
(www.boomdigitale.it)
0.0 KiB
…js/swup.min.js:1:3327
(www.boomdigitale.it)
@babel/plugin-transform-classes
Unattributable
0.1 KiB
/modules.ef5986d….js
(script.hotjar.com)
0.1 KiB
/modules.ef5986d….js:4:80682
(script.hotjar.com)
@babel/plugin-transform-classes
/c/hotjar-3907077.js?sv=7
(static.hotjar.com)
0.1 KiB
/c/hotjar-3907077.js?sv=7:3:921
(static.hotjar.com)
@babel/plugin-transform-classes
iubenda
utility
0.0 KiB
…1.76.2/core-it.js
(cdn.iubenda.com)
0.0 KiB
…1.76.2/core-it.js:1:580
(cdn.iubenda.com)
@babel/plugin-transform-classes
Avoid an excessive DOM size 923 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
923
Maximum DOM Depth
div.wp-block-column > ul.wp-block-list > li > a
<a href="https://www.boomdigitale.it/realizzazione-siti-web-roma/">
17
Maximum Child Elements
body.home
<body class="home page-template-default page page-id-3726 wp-embed-responsive swup-enab…">
51
Avoid large layout shifts 4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
0.000
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
0.000
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
0.000
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
0.000
Avoid non-composited animations 4 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
e se trasformassimo la tua idea in un sito web?
<h1>
Unsupported CSS Property: background-position-x
colorwave
Boom Digitale
<div class="header-top transition-up">
Unsupported CSS Property: top
top
Verificato da Trustindex
<div class="ti-sticky-button-footer">
Unsupported CSS Property: max-height
max-height
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
Unsupported CSS Property: margin-left
margin-left
Unsupported CSS Property: box-shadow
box-shadow
Avoid chaining critical requests 30 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 623.081 ms
Initial Navigation
https://www.boomdigitale.it
…newsletter/style.css?ver=8.7.1
(www.boomdigitale.it)
- 168.103 ms, 1.91 KiB
…jquery/jquery.min.js?ver=3.7.1
(www.boomdigitale.it)
- 238.163 ms, 30.16 KiB
…jquery/jquery-migrate.min.js?ver=3.4.1
(www.boomdigitale.it)
- 100.479 ms, 5.26 KiB
…js/app.js?ver=4.17
(www.boomdigitale.it)
- 162.846 ms, 3.50 KiB
…dist/hooks.min.js?ver=4d63a3d…
(www.boomdigitale.it)
- 233.642 ms, 2.11 KiB
…dist/i18n.min.js?ver=5e580eb…
(www.boomdigitale.it)
- 180.897 ms, 4.08 KiB
…js/index.js?ver=6.0.4
(www.boomdigitale.it)
- 121.746 ms, 3.92 KiB
…js/index.js?ver=6.0.4
(www.boomdigitale.it)
- 135.125 ms, 4.67 KiB
…js/main.js
(www.boomdigitale.it)
- 101.055 ms, 1.22 KiB
/autoblocking/3318616.js
(cs.iubenda.com)
- 166.132 ms, 11.84 KiB
…js/lazysizes.min.js
(www.boomdigitale.it)
- 203.155 ms, 3.80 KiB
…js/ls.unveilhooks.min.js
(www.boomdigitale.it)
- 118.207 ms, 1.27 KiB
…js/swup.min.js
(www.boomdigitale.it)
- 101.227 ms, 5.38 KiB
…js/SwupBodyClassPlugin.min.js
(www.boomdigitale.it)
- 147.044 ms, 1.80 KiB
…js/SwupHeadPlugin.min.js
(www.boomdigitale.it)
- 223.322 ms, 2.18 KiB
…js/SwupScrollPlugin.min.js
(www.boomdigitale.it)
- 98.995 ms, 2.70 KiB
…js/SwupStylesPlugin.min.js
(www.boomdigitale.it)
- 189.145 ms, 2.03 KiB
…js/masonry.min.js
(www.boomdigitale.it)
- 224.101 ms, 7.69 KiB
…js/scrollmagic.js
(www.boomdigitale.it)
- 140.769 ms, 6.42 KiB
…css/main.css?ver=4.17
(www.boomdigitale.it)
- 62.084 ms, 1.07 KiB
…js/scrolltoplugin.min.js
(www.boomdigitale.it)
- 100.853 ms, 2.08 KiB
…js/tweenmax.min.js
(www.boomdigitale.it)
- 189.651 ms, 39.34 KiB
…js/functions.js
(www.boomdigitale.it)
- 141.231 ms, 2.80 KiB
…block-library/style.min.css?ver=6.7.2
(www.boomdigitale.it)
- 238.49 ms, 15.31 KiB
…css/styles.css?ver=6.0.4
(www.boomdigitale.it)
- 235.542 ms, 1.48 KiB
…css/swiper.min.css?ver=6.7.2
(www.boomdigitale.it)
- 83.785 ms, 5.23 KiB
…css/fancybox.min.css?ver=6.7.2
(www.boomdigitale.it)
- 201.324 ms, 3.05 KiB
…css/main.css?ver=6.7.2
(www.boomdigitale.it)
- 153.707 ms, 0.82 KiB
…css/main.css?ver=6.7.2
(www.boomdigitale.it)
…fonts/HKGrotesk-Regular.woff2
(www.boomdigitale.it)
- 64.653 ms, 33.05 KiB
…fonts/HKGrotesk-Bold.woff2
(www.boomdigitale.it)
- 66.933 ms, 32.43 KiB
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
iubenda
utility
86 KiB
3 ms
/autoblocking/3318616.js
(cs.iubenda.com)
12 KiB
3 ms
…1.76.2/core-it.js
(cdn.iubenda.com)
71 KiB
0 ms
/cs/iubenda_cs.js?ver=3.12.1
(cdn.iubenda.com)
1 KiB
0 ms
…js/82105649.js
(cs.iubenda.com)
1 KiB
0 ms
/csdata?db=hits1
(idb.iubenda.com)
1 KiB
0 ms
trustindex.io
134 KiB
0 ms
…js/cert-translations.js
(cdn.trustindex.io)
60 KiB
0 ms
/loader.js
(cdn.trustindex.io)
16 KiB
0 ms
…opensans/latin2.woff2
(cdn.trustindex.io)
15 KiB
0 ms
…opensans/latin.woff2
(cdn.trustindex.io)
15 KiB
0 ms
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
5 KiB
0 ms
…icon/ti-cert-excellent-service.svg
(cdn.trustindex.io)
4 KiB
0 ms
…widget-presetted-css/74-default.css
(cdn.trustindex.io)
4 KiB
0 ms
…ce26da6…/content.html
(cdn.trustindex.io)
3 KiB
0 ms
…icon/ti-cert-ssl.svg
(cdn.trustindex.io)
3 KiB
0 ms
…Trustindex/logo.svg
(cdn.trustindex.io)
3 KiB
0 ms
…Google/logo.svg
(cdn.trustindex.io)
2 KiB
0 ms
…Trustindex/icon.svg
(cdn.trustindex.io)
2 KiB
0 ms
…star/f.svg
(cdn.trustindex.io)
2 KiB
0 ms
…star/f.svg
(cdn.trustindex.io)
2 KiB
0 ms
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
iubenda
utility
53 ms
/autoblocking/3318616.js
(cs.iubenda.com)
1,949 ms
53 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (23)
Show Hide
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
WordPressUpload images directly through the media library to ensure that the required image sizes are available, and then insert them from the media library or use the image widget to ensure the optimal image sizes are used (including those for the responsive breakpoints). Avoid using Full Size images unless the dimensions are adequate for their usage. Learn More.
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
WordPressInstall a lazy-load WordPress plugin that provides the ability to defer any offscreen images, or switch to a theme that provides that functionality. Also consider using the AMP plugin.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
WordPressA number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your styles. You may also want to use a build process to do this minification up-front if possible.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
WordPressA number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your scripts. You may also want to use a build process to do this minification up front if possible.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
WordPressConsider using an image optimization WordPress plugin that compresses your images while retaining quality.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
WordPressConsider using the Performance Lab plugin to automatically convert your uploaded JPEG images into WebP, wherever supported.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
WordPressYou can enable text compression in your web server configuration.
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Initial server response time was short Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
WordPressChoose a lightweight theme (ideally a block theme) and implement full-page caching or a static site solution. Disable unnecessary plugins to minimize server overhead. Consider upgrading your hosting to managed or dedicated service.
URL
Time Spent
boomdigitale.it
1st party
100 ms
https://www.boomdigitale.it
100 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
WordPressConsider uploading your GIF to a service which will make it available to embed as an HTML5 video.
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Avoids enormous network payloads Total size was 544 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
WordPressConsider showing excerpts in your post lists (e.g. via the more tag), reducing the number of posts shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.
URL
Transfer Size
boomdigitale.it
1st party
209.6 KiB
…11/adr-general-contract-aversa-agenzia-web-boom-digitale-….webp
(www.boomdigitale.it)
47.4 KiB
…js/tweenmax.min.js
(www.boomdigitale.it)
39.3 KiB
…fonts/HKGrotesk-Regular.woff2
(www.boomdigitale.it)
33.1 KiB
…fonts/HKGrotesk-Bold.woff2
(www.boomdigitale.it)
32.4 KiB
…jquery/jquery.min.js?ver=3.7.1
(www.boomdigitale.it)
30.2 KiB
https://www.boomdigitale.it
27.2 KiB
trustindex.io
90.6 KiB
…js/cert-translations.js
(cdn.trustindex.io)
59.5 KiB
/loader.js
(cdn.trustindex.io)
15.6 KiB
…opensans/latin2.woff2
(cdn.trustindex.io)
15.5 KiB
iubenda
utility
71.0 KiB
…1.76.2/core-it.js
(cdn.iubenda.com)
71.0 KiB
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
boomdigitale.it
1st party
766 ms
152 ms
5 ms
https://www.boomdigitale.it
459 ms
15 ms
3 ms
…jquery/jquery.min.js?ver=3.7.1
(www.boomdigitale.it)
252 ms
118 ms
2 ms
…js/lazysizes.min.js
(www.boomdigitale.it)
55 ms
19 ms
0 ms
iubenda
utility
545 ms
316 ms
10 ms
/autoblocking/3318616.js
(cs.iubenda.com)
471 ms
257 ms
2 ms
…1.76.2/core-it.js
(cdn.iubenda.com)
73 ms
59 ms
9 ms
Unattributable
108 ms
3 ms
0 ms
Unattributable
108 ms
3 ms
0 ms
trustindex.io
60 ms
13 ms
0 ms
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
60 ms
13 ms
0 ms
Minimizes main-thread work 1.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
554 ms
Style & Layout
499 ms
Other
329 ms
Rendering
128 ms
Parse HTML & CSS
66 ms
Script Parsing & Compilation
29 ms
Garbage Collection
3 ms
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
100
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (30)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (27)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
96
Best Practices
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
boomdigitale.it
1st party
…js/main.js:70:4
(www.boomdigitale.it)
ReferenceError: Fancybox is not defined
    at Object.fancyboxInit (https://www.boomdigitale.it/contenuti/plugins/themerain-core/assets/js/main.js:70:5)
    at Object.init (https://www.boomdigitale.it/contenuti/plugins/themerain-core/assets/js/main.js:4:10)
    at https://www.boomdigitale.it/contenuti/plugins/themerain-core/assets/js/main.js:78:15
Unattributable
/modules.ef5986d….js:4:126317
(script.hotjar.com)
WebSocket connection to 'wss://ws.hotjar.com/api/v2/client/ws?v=7&site_id=3907077' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.7.1
GreenSock JS
2.1.3
ScrollMagic
2.0.7
WordPress
6.7.2
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No HSTS header found
High
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Description
Severity
No frame control policy found
High
Passed audits (14)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 99.97% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
trustindex.io
…widget-presetted-css/74-default.css:1:7980
(cdn.trustindex.io)
.ti-widget[data-layout-id='74'][data-set-id='default'] .ti-sticky-button .ti-sticky-button-footer .ti-sticky-button-footer-inner
0.03%
9.65px
Unattributable
Legible text
99.97%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
trustindex.io
/loader.js
(cdn.trustindex.io)
/loader.js.map
(cdn.trustindex.io)
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
/loader-cert.js.map
(cdn.trustindex.io)
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
No Data
Diagnose performance issues
98
Performance
97
Accessibility
96
Best Practices
100
SEO
98
Performance
97
Accessibility
96
Best Practices
100
SEO
98 FCP+10LCP+24TBT+30CLS+25SI+10 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 13, 2025, 10:11 AM UTC
  • Emulated Desktop with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 497 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: Europe
  • Using HeadlessChromium 133.0.6943.141 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Eliminate render-blocking resources Potential savings of 400 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
WordPressThere are a number of WordPress plugins that can help you inline critical assets or defer less important resources. Beware that optimizations provided by these plugins may break features of your theme or plugins, so you will likely need to make code changes.
URL
Transfer Size
Potential Savings
boomdigitale.it
1st party
39.3 KiB
80 ms
…js/tweenmax.min.js
(www.boomdigitale.it)
39.3 KiB
80 ms
iubenda
utility
11.8 KiB
240 ms
/autoblocking/3318616.js
(cs.iubenda.com)
11.8 KiB
240 ms
Reduce unused CSS Potential savings of 15 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
WordPressConsider reducing, or switching, the number of WordPress plugins loading unused CSS in your page. To identify plugins that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a stylesheet if it is actually used on the page.
URL
Transfer Size
Potential Savings
boomdigitale.it
1st party
14.7 KiB
14.5 KiB
…block-library/style.min.css?ver=6.7.2
(www.boomdigitale.it)
14.7 KiB
14.5 KiB
Reduce unused JavaScript Potential savings of 145 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
WordPressConsider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your page. To identify plugins that are adding extraneous JS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the script. Look out for plugins that have many scripts in the list which have a lot of red in code coverage. A plugin should only enqueue a script if it is actually used on the page.
URL
Transfer Size
Potential Savings
Unattributable
173.3 KiB
84.1 KiB
/gtm.js?id=GTM-PZ7Q74B9
(www.googletagmanager.com)
99.5 KiB
49.0 KiB
/modules.ef5986d….js
(script.hotjar.com)
73.7 KiB
35.1 KiB
iubenda
utility
70.1 KiB
31.0 KiB
…1.76.2/core-it.js
(cdn.iubenda.com)
70.1 KiB
31.0 KiB
boomdigitale.it
1st party
38.7 KiB
29.6 KiB
…js/tweenmax.min.js
(www.boomdigitale.it)
38.7 KiB
29.6 KiB
Serve static assets with an efficient cache policy 7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
WordPressRead about Browser Caching in WordPress.
URL
Cache TTL
Transfer Size
trustindex.io
85 KiB
…js/cert-translations.js
(cdn.trustindex.io)
None
60 KiB
/loader.js
(cdn.trustindex.io)
None
16 KiB
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
None
5 KiB
…widget-presetted-css/74-default.css
(cdn.trustindex.io)
None
4 KiB
iubenda
utility
14 KiB
/autoblocking/3318616.js
(cs.iubenda.com)
1h
12 KiB
/cs/iubenda_cs.js?ver=3.12.1
(cdn.iubenda.com)
1h
1 KiB
…js/82105649.js
(cs.iubenda.com)
1h
1 KiB
Properly size images Potential savings of 165 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
WordPressUpload images directly through the media library to ensure that the required image sizes are available, and then insert them from the media library or use the image widget to ensure the optimal image sizes are used (including those for the responsive breakpoints). Avoid using Full Size images unless the dimensions are adequate for their usage. Learn More.
URL
Resource Size
Potential Savings
WordPress
hosting
187.0 KiB
124.9 KiB
APO Group - Aversa - Napoli - Ristrutturazione Locali - Agenzia Web Boom Digita…
<img decoding="async" loading="lazy" data-src="https://i0.wp.com/www.boomdigitale.it/contenuti/uploads/2024/10/apo-group-…" class=" lazyloaded" alt="APO Group - Aversa - Napoli - Ristrutturazione Locali - Agenzia Web Boom D…" data-srcset="https://i0.wp.com/www.boomdigitale.it/contenuti/uploads/2024/10/apo-group-…" data-cmp-info="10" srcset="https://i0.wp.com/www.boomdigitale.it/contenuti/uploads/2024/10/apo-group-…" src="https://i0.wp.com/www.boomdigitale.it/contenuti/uploads/2024/10/apo-group-…">
…10/apo-group-aversa-agenzia-web-boom-digitale-napoli-si….webp?…
(i0.wp.com)
187.0 KiB
124.9 KiB
boomdigitale.it
1st party
76.4 KiB
40.0 KiB
ADR General Contract - Aversa - Caserta - Ristrutturazioni chiavi in mano - Age…
<img decoding="async" loading="lazy" data-src="https://www.boomdigitale.it/contenuti/uploads/2024/11/adr-general-contract…" class="ls-is-cached lazyloaded" alt="ADR General Contract - Aversa - Caserta - Ristrutturazioni chiavi in mano …" data-srcset="https://www.boomdigitale.it/contenuti/uploads/2024/11/adr-general-contract…" srcset="https://www.boomdigitale.it/contenuti/uploads/2024/11/adr-general-contract…" src="https://www.boomdigitale.it/contenuti/uploads/2024/11/adr-general-contract…" data-cmp-info="10">
…11/adr-general-contract-aversa-agenzia-web-boom-digitale-….webp
(www.boomdigitale.it)
76.4 KiB
40.0 KiB
Remove duplicate modules in JavaScript bundles Potential savings of 1 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Source
Transfer Size
Potential Savings
webpack://trustindex/./web/dev/js/loader/TrustindexCommon.js
0 KiB
/loader.js
(cdn.trustindex.io)
0 KiB
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
0 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
boomdigitale.it
1st party
0.3 KiB
…js/SwupHeadPlugin.min.js
(www.boomdigitale.it)
0.1 KiB
…js/SwupHeadPlugin.min.js:1:1813
(www.boomdigitale.it)
@babel/plugin-transform-classes
…js/SwupBodyClassPlugin.min.js
(www.boomdigitale.it)
0.1 KiB
…js/SwupBodyClassPlugin.min.js:1:1995
(www.boomdigitale.it)
@babel/plugin-transform-classes
…js/SwupStylesPlugin.min.js
(www.boomdigitale.it)
0.1 KiB
…js/SwupStylesPlugin.min.js:1:1817
(www.boomdigitale.it)
@babel/plugin-transform-classes
…js/SwupScrollPlugin.min.js
(www.boomdigitale.it)
0.1 KiB
…js/SwupScrollPlugin.min.js:1:2011
(www.boomdigitale.it)
@babel/plugin-transform-classes
…js/swup.min.js
(www.boomdigitale.it)
0.0 KiB
…js/swup.min.js:1:3327
(www.boomdigitale.it)
@babel/plugin-transform-classes
Unattributable
0.1 KiB
/modules.ef5986d….js
(script.hotjar.com)
0.1 KiB
/modules.ef5986d….js:4:80682
(script.hotjar.com)
@babel/plugin-transform-classes
/c/hotjar-3907077.js?sv=7
(static.hotjar.com)
0.1 KiB
/c/hotjar-3907077.js?sv=7:3:921
(static.hotjar.com)
@babel/plugin-transform-classes
iubenda
utility
0.0 KiB
…1.76.2/core-it.js
(cdn.iubenda.com)
0.0 KiB
…1.76.2/core-it.js:1:580
(cdn.iubenda.com)
@babel/plugin-transform-classes
Avoid an excessive DOM size 923 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
923
Maximum DOM Depth
div.wp-block-column > ul.wp-block-list > li > a
<a href="https://www.boomdigitale.it/realizzazione-siti-web-roma/">
17
Maximum Child Elements
body.home
<body class="home page-template-default page page-id-3726 wp-embed-responsive swup-enab…">
51
Avoid large layout shifts 9 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Boom Digitale Web Agency Napoli e Roma +39 320 4521 570 ciao@boomdigitale.it C…
<div class="header-top transition-up">
0.000
Web Agency Napoli e Roma +39 320 4521 570 ciao@boomdigitale.it Chiedi un preven…
<div class="site-info">
0.000
Boom Digitale Web Agency Napoli e Roma +39 320 4521 570 ciao@boomdigitale.it C…
<div class="header-top transition-up">
0.000
body.home > div#ht-ctc-chat
<div class="ht-ctc ht-ctc-chat ctc-analytics ctc_wp_desktop style-2 ht_ctc_entry_anima…" id="ht-ctc-chat" style="position: fixed; bottom: 53px; right: 30px; cursor: pointer;">
0.000
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
0.000
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
0.000
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
0.000
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
0.000
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
0.000
Avoid non-composited animations 4 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
e se trasformassimo la tua idea in un sito web?
<h1>
Unsupported CSS Property: background-position-x
colorwave
Boom Digitale Web Agency Napoli e Roma +39 320 4521 570 ciao@boomdigitale.it C…
<div class="header-top transition-up">
Unsupported CSS Property: top
top
Verificato da Trustindex
<div class="ti-sticky-button-footer">
Unsupported CSS Property: max-height
max-height
Servizio Eccellente Verificato da Trustindex
<div class="ti-sticky-button ti-position-right-vertical ti-type-01">
Unsupported CSS Property: margin-left
margin-left
Unsupported CSS Property: box-shadow
box-shadow
Avoid chaining critical requests 30 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 819.76 ms
Initial Navigation
https://www.boomdigitale.it
…newsletter/style.css?ver=8.7.1
(www.boomdigitale.it)
- 256.248 ms, 1.91 KiB
…jquery/jquery.min.js?ver=3.7.1
(www.boomdigitale.it)
- 381.573 ms, 30.16 KiB
…jquery/jquery-migrate.min.js?ver=3.4.1
(www.boomdigitale.it)
- 255.139 ms, 5.26 KiB
…js/app.js?ver=4.17
(www.boomdigitale.it)
- 334.972 ms, 3.50 KiB
…dist/hooks.min.js?ver=4d63a3d…
(www.boomdigitale.it)
- 302.059 ms, 2.11 KiB
…dist/i18n.min.js?ver=5e580eb…
(www.boomdigitale.it)
- 302.545 ms, 4.08 KiB
…js/index.js?ver=6.0.4
(www.boomdigitale.it)
- 349.638 ms, 3.92 KiB
…js/index.js?ver=6.0.4
(www.boomdigitale.it)
- 221.008 ms, 4.67 KiB
…js/main.js
(www.boomdigitale.it)
- 280.219 ms, 1.22 KiB
/autoblocking/3318616.js
(cs.iubenda.com)
- 266.348 ms, 11.85 KiB
…js/lazysizes.min.js
(www.boomdigitale.it)
- 177.812 ms, 3.80 KiB
…js/ls.unveilhooks.min.js
(www.boomdigitale.it)
- 279.095 ms, 1.27 KiB
…js/swup.min.js
(www.boomdigitale.it)
- 178.729 ms, 5.38 KiB
…js/SwupBodyClassPlugin.min.js
(www.boomdigitale.it)
- 274.986 ms, 1.80 KiB
…js/SwupHeadPlugin.min.js
(www.boomdigitale.it)
- 283.276 ms, 2.18 KiB
…js/SwupScrollPlugin.min.js
(www.boomdigitale.it)
- 301.642 ms, 2.70 KiB
…js/SwupStylesPlugin.min.js
(www.boomdigitale.it)
- 277.118 ms, 2.03 KiB
…js/masonry.min.js
(www.boomdigitale.it)
- 328.932 ms, 7.69 KiB
…js/scrollmagic.js
(www.boomdigitale.it)
- 300.9 ms, 6.42 KiB
…css/main.css?ver=4.17
(www.boomdigitale.it)
- 281.595 ms, 1.07 KiB
…js/scrolltoplugin.min.js
(www.boomdigitale.it)
- 299.758 ms, 2.08 KiB
…js/tweenmax.min.js
(www.boomdigitale.it)
- 401.143 ms, 39.34 KiB
…js/functions.js
(www.boomdigitale.it)
- 322.988 ms, 2.80 KiB
…block-library/style.min.css?ver=6.7.2
(www.boomdigitale.it)
- 225.546 ms, 15.31 KiB
…css/styles.css?ver=6.0.4
(www.boomdigitale.it)
- 181.339 ms, 1.48 KiB
…css/swiper.min.css?ver=6.7.2
(www.boomdigitale.it)
- 306.367 ms, 5.23 KiB
…css/fancybox.min.css?ver=6.7.2
(www.boomdigitale.it)
- 329.619 ms, 3.05 KiB
…css/main.css?ver=6.7.2
(www.boomdigitale.it)
- 284.748 ms, 0.82 KiB
…css/main.css?ver=6.7.2
(www.boomdigitale.it)
…fonts/HKGrotesk-Regular.woff2
(www.boomdigitale.it)
- 66.862 ms, 33.05 KiB
…fonts/HKGrotesk-Bold.woff2
(www.boomdigitale.it)
- 79.72 ms, 32.43 KiB
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
WordPress
hosting
190 KiB
0 ms
…10/apo-group-aversa-agenzia-web-boom-digitale-napoli-si….webp?…
(i0.wp.com)
188 KiB
0 ms
…10/tari-architects-roma-agenzia-web-boom-digitale-napoli….png?…
(i0.wp.com)
2 KiB
0 ms
trustindex.io
134 KiB
0 ms
…js/cert-translations.js
(cdn.trustindex.io)
60 KiB
0 ms
/loader.js
(cdn.trustindex.io)
16 KiB
0 ms
…opensans/latin2.woff2
(cdn.trustindex.io)
15 KiB
0 ms
…opensans/latin.woff2
(cdn.trustindex.io)
15 KiB
0 ms
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
5 KiB
0 ms
…icon/ti-cert-excellent-service.svg
(cdn.trustindex.io)
4 KiB
0 ms
…widget-presetted-css/74-default.css
(cdn.trustindex.io)
4 KiB
0 ms
…ce26da6…/content.html
(cdn.trustindex.io)
3 KiB
0 ms
…icon/ti-cert-ssl.svg
(cdn.trustindex.io)
3 KiB
0 ms
…Trustindex/logo.svg
(cdn.trustindex.io)
3 KiB
0 ms
…Google/logo.svg
(cdn.trustindex.io)
2 KiB
0 ms
…Trustindex/icon.svg
(cdn.trustindex.io)
2 KiB
0 ms
…star/f.svg
(cdn.trustindex.io)
2 KiB
0 ms
…star/f.svg
(cdn.trustindex.io)
2 KiB
0 ms
iubenda
utility
86 KiB
0 ms
…1.76.2/core-it.js
(cdn.iubenda.com)
71 KiB
0 ms
/autoblocking/3318616.js
(cs.iubenda.com)
12 KiB
0 ms
/cs/iubenda_cs.js?ver=3.12.1
(cdn.iubenda.com)
1 KiB
0 ms
…js/82105649.js
(cs.iubenda.com)
1 KiB
0 ms
/csdata?db=hits1
(idb.iubenda.com)
1 KiB
0 ms
Largest Contentful Paint element 1,030 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
e se trasformassimo la tua idea in un sito web?
<h1>
Phase
% of LCP
Timing
TTFB
16%
160 ms
Load Delay
0%
0 ms
Load Time
0%
0 ms
Render Delay
84%
870 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (23)
Show Hide
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
WordPressInstall a lazy-load WordPress plugin that provides the ability to defer any offscreen images, or switch to a theme that provides that functionality. Also consider using the AMP plugin.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
WordPressA number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your styles. You may also want to use a build process to do this minification up-front if possible.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
WordPressA number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your scripts. You may also want to use a build process to do this minification up front if possible.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
WordPressConsider using an image optimization WordPress plugin that compresses your images while retaining quality.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
WordPressConsider using the Performance Lab plugin to automatically convert your uploaded JPEG images into WebP, wherever supported.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
WordPressYou can enable text compression in your web server configuration.
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Initial server response time was short Root document took 60 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
WordPressChoose a lightweight theme (ideally a block theme) and implement full-page caching or a static site solution. Disable unnecessary plugins to minimize server overhead. Consider upgrading your hosting to managed or dedicated service.
URL
Time Spent
boomdigitale.it
1st party
60 ms
https://www.boomdigitale.it
60 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
WordPressConsider uploading your GIF to a service which will make it available to embed as an HTML5 video.
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Avoids enormous network payloads Total size was 776 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
WordPressConsider showing excerpts in your post lists (e.g. via the more tag), reducing the number of posts shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.
URL
Transfer Size
boomdigitale.it
1st party
260.0 KiB
…11/adr-general-contract-aversa-agenzia-web-boom-digitale-….webp
(www.boomdigitale.it)
76.9 KiB
…js/tweenmax.min.js
(www.boomdigitale.it)
39.3 KiB
…fonts/HKGrotesk-Regular.woff2
(www.boomdigitale.it)
33.1 KiB
…fonts/HKGrotesk-Bold.woff2
(www.boomdigitale.it)
32.4 KiB
…jquery/jquery.min.js?ver=3.7.1
(www.boomdigitale.it)
30.2 KiB
https://www.boomdigitale.it
27.2 KiB
…01/preventivo-sito-web-realizzazione-siti-wordpress-1536x8….jpg
(www.boomdigitale.it)
20.9 KiB
WordPress
hosting
187.6 KiB
…10/apo-group-aversa-agenzia-web-boom-digitale-napoli-si….webp?…
(i0.wp.com)
187.6 KiB
iubenda
utility
71.0 KiB
…1.76.2/core-it.js
(cdn.iubenda.com)
71.0 KiB
trustindex.io
59.5 KiB
…js/cert-translations.js
(cdn.trustindex.io)
59.5 KiB
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
boomdigitale.it
1st party
762 ms
132 ms
5 ms
https://www.boomdigitale.it
487 ms
7 ms
2 ms
…jquery/jquery.min.js?ver=3.7.1
(www.boomdigitale.it)
134 ms
91 ms
1 ms
…js/tweenmax.min.js
(www.boomdigitale.it)
74 ms
15 ms
2 ms
…js/lazysizes.min.js
(www.boomdigitale.it)
66 ms
19 ms
0 ms
iubenda
utility
274 ms
197 ms
9 ms
/autoblocking/3318616.js
(cs.iubenda.com)
213 ms
145 ms
4 ms
…1.76.2/core-it.js
(cdn.iubenda.com)
61 ms
52 ms
4 ms
Unattributable
97 ms
2 ms
0 ms
Unattributable
97 ms
2 ms
0 ms
trustindex.io
54 ms
10 ms
0 ms
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
54 ms
10 ms
0 ms
Minimizes main-thread work 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
383 ms
Style & Layout
360 ms
Other
322 ms
Rendering
138 ms
Parse HTML & CSS
47 ms
Script Parsing & Compilation
22 ms
Garbage Collection
4 ms
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid long main-thread tasks
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
97
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Best practices
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
Web Agency Napoli
<a class="cool-link" href="https://www.boomdigitale.it/realizzazione-siti-web-napoli/">
+39 320 4521 570
<a class="cool-link" href="https://wa.me/message/FOGJCK3BTAJ3I1" data-cmp-ab="2">
+39 320 4521 570
<a class="cool-link" href="https://wa.me/message/FOGJCK3BTAJ3I1" data-cmp-ab="2">
Web Agency Napoli
<a class="cool-link" href="https://www.boomdigitale.it/realizzazione-siti-web-napoli/">
ciao@boomdigitale.it
<a class="cool-link" href="mailto:ciao@boomdigitale.it" data-cmp-ab="2">
ciao@boomdigitale.it
<a class="cool-link" href="mailto:ciao@boomdigitale.it" data-cmp-ab="2">
+39 320 4521 570
<a class="cool-link" href="https://wa.me/message/FOGJCK3BTAJ3I1" data-cmp-ab="2">
Chiedi un preventivo
<a class="cool-link" href="https://www.boomdigitale.it/preventivo-sito-web#preventivo">
Chiedi un preventivo
<a class="cool-link" href="https://www.boomdigitale.it/preventivo-sito-web#preventivo">
ciao@boomdigitale.it
<a class="cool-link" href="mailto:ciao@boomdigitale.it" data-cmp-ab="2">
Servizi
<a href="#">
Progetti e Siti Web
<a href="https://www.boomdigitale.it/progetti-siti-web/">
Chi siamo
<a href="https://www.boomdigitale.it/chi-siamo/">
Chi siamo
<a href="https://www.boomdigitale.it/chi-siamo/">
Servizi
<a href="#">
Contatti
<a href="https://www.boomdigitale.it/contatti/">
Contatti
<a href="https://www.boomdigitale.it/contatti/">
Chi siamo
<a href="https://www.boomdigitale.it/chi-siamo/">
Blog
<a href="https://www.boomdigitale.it/blog/">
Blog
<a href="https://www.boomdigitale.it/blog/">
Contatti
<a href="https://www.boomdigitale.it/contatti/">
These items highlight common accessibility best practices.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (29)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (27)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
96
Best Practices
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
boomdigitale.it
1st party
…js/main.js:70:4
(www.boomdigitale.it)
ReferenceError: Fancybox is not defined
    at Object.fancyboxInit (https://www.boomdigitale.it/contenuti/plugins/themerain-core/assets/js/main.js:70:5)
    at Object.init (https://www.boomdigitale.it/contenuti/plugins/themerain-core/assets/js/main.js:4:10)
    at https://www.boomdigitale.it/contenuti/plugins/themerain-core/assets/js/main.js:78:15
Unattributable
/modules.ef5986d….js:4:126317
(script.hotjar.com)
WebSocket connection to 'wss://ws.hotjar.com/api/v2/client/ws?v=7&site_id=3907077' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.7.1
GreenSock JS
2.1.3
ScrollMagic
2.0.7
WordPress
6.7.2
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No HSTS header found
High
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Description
Severity
No frame control policy found
High
Passed audits (13)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
trustindex.io
/loader.js
(cdn.trustindex.io)
/loader.js.map
(cdn.trustindex.io)
/loader-cert.js?ce26da6…
(cdn.trustindex.io)
/loader-cert.js.map
(cdn.trustindex.io)
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.