digital360.it

digital360.it is SSL secured

Free website and domain report on digital360.it

Last Updated: 24th January, 2022 Update Now
Overview

Snoop Summary for digital360.it

This is a free and comprehensive report about digital360.it. The domain digital360.it is currently hosted on a server located in Dublin, Leinster in Ireland with the IP address 63.33.230.128, where EUR is the local currency and the local language is English. If digital360.it was to be sold it would possibly be worth $258 USD (based on the daily revenue potential of the website over a 24 month period). Digital360.it receives an estimated 119 unique visitors every day - a decent amount of traffic! This report was last updated 24th January, 2022.

About digital360.it

Site Preview: digital360.it digital360.it
Title: Digital360 - Empowering Innovation
Description: Siamo una realtà imprenditoriale nata dalla ricerca universitaria, oltre 200 talenti con un obiettivo comune: contribuire a Trasformazione Digitale e Innovazione in Italia
Keywords and Tags: business
Related Terms: averotica nata, ero nata, innovazione, innovazione sociale, innovazione sostenibile, libreria universitaria, obiettivo, spedire pacchi dalla cina in italia, universitaria, visioni e innovazione
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$258 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,868,881
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 119
Monthly Visitors: 3,622
Yearly Visitors: 43,435
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $10 USD
Yearly Revenue: $124 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: digital360.it 13
Domain Name: digital360 10
Extension (TLD): it 2

Page Speed Analysis

Average Load Time: 0.52 seconds
Load Time Comparison: Faster than 95% of sites

PageSpeed Insights

Avg. (All Categories) 85
Performance 86
Accessibility 87
Best Practices 87
SEO 92
Progressive Web App 73
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.digital360.it/
Updated: 28th July, 2021

2.24 seconds
First Contentful Paint (FCP)
72%
5%
23%

0.00 seconds
First Input Delay (FID)
98%
2%
0%

Simulate loading on desktop
86

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for digital360.it. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 1.5 s
The time taken for the page to become fully interactive.
Total Blocking Time — 90 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Opportunities

Eliminate render-blocking resources — Potential savings of 120 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Digital360.it should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Titillium+Web%3Aital%2Cwght%400%2C300%3B0%2C400%3B0%2C600%3B0%2C700%3B1%2C300%3B1%2C400%3B1%2C600%3B1%2C700&display=swap&ver=1.0.6
1338
230
Properly size images — Potential savings of 50 KiB
Images can slow down the page's load time. Digital360.it should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.digital360.it/wp-content/uploads/2021/06/bg-career-1.jpg.webp
56534
31690
https://media.digital360.it/wp-content/uploads/2021/05/29100037/Gabriele-Faggioli.jpg.webp
10134
7419
https://media.digital360.it/wp-content/uploads/2021/07/14181954/AndreaRangonePresidenteDIGITAL360.jpg.webp
13454
7072
https://media.digital360.it/wp-content/uploads/2021/05/29095758/logo-digital360-gradient.png.webp
6166
5207
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Digital360.it should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Digital360.it should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Digital360.it should consider minifying JS files.
Reduce unused CSS — Potential savings of 120 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Digital360.it should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/02f41.css?x21018
118727
112522
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/a5ff7.css?x21018
10652
10652
Reduce unused JavaScript — Potential savings of 38 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
82133
39251
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 330 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.digital360.it/
328.208
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Digital360.it should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/882cf.js?x21018
54
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
48
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 726 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/02f41.css?x21018
118727
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fonts/ionicons.ttf?v=2.0.1&x44622
110439
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
82133
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fontawesome/webfonts/fa-brands-400.woff2
77439
https://www.digital360.it/wp-content/uploads/2021/06/bg-career-1.jpg.webp
56994
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
34906
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel-shadowed.png?x44622
31737
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/page-header-pixels.png?x44622
29967
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel-benefit.png?x44622
15234
https://www.digital360.it/
14823
Uses efficient cache policy on static assets — 1 resource found
Digital360.it can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://cdnd360.it/networkdigital360/ND360_Logo_POS.svg
259200000
1849
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Digital360.it should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
352.278
170.315
7.083
https://www.digital360.it/
237.94
7.326
3.405
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
237.71
118.109
1.741
Unattributable
66.324
2.814
0.157
Minimizes main-thread work — 0.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
354.76
Script Evaluation
300.705
Other
155.784
Rendering
52.129
Parse HTML & CSS
48.413
Script Parsing & Compilation
14.114
Keep request counts low and transfer sizes small — 35 requests • 726 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
35
743908
Font
8
256516
Image
17
199354
Script
4
141706
Stylesheet
3
130717
Document
1
14823
Other
2
792
Media
0
0
Third-party
22
625080
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
67883
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.056046413436127
0.038531909237337
0.0091075421833706
0.0055092899045618
0.0055092899045618
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 4 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
1534
134
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
1407
85
https://www.digital360.it/
216
64
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
894
60
Avoid non-composited animations — 35 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://digital360.it/
http/1.1
0
198.33400007337
321
0
301
text/html
https://digital360.it/
http/1.1
199.8860000167
895.42399998754
471
0
301
text/html
https://www.digital360.it/
h2
895.99500014447
1223.2060001697
14823
76000
200
text/html
Document
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
h2
1234.1130001005
1333.5979999974
34906
100747
200
application/x-javascript
Script
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
h2
1234.4270001631
1341.6100000031
82133
288561
200
application/x-javascript
Script
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/882cf.js?x21018
h2
1234.7089999821
1330.2430000622
11938
40573
200
application/x-javascript
Script
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/e0515.js?x21018
h2
1236.7440001108
1322.5100000855
12729
39783
200
application/x-javascript
Script
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/a5ff7.css?x21018
h2
1236.9590001181
1336.3420001697
10652
80557
200
text/css
Stylesheet
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/02f41.css?x21018
h2
1237.1710001025
1370.9540001582
118727
664311
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Titillium+Web%3Aital%2Cwght%400%2C300%3B0%2C400%3B0%2C600%3B0%2C700%3B1%2C300%3B1%2C400%3B1%2C600%3B1%2C700&display=swap&ver=1.0.6
h2
1246.2540001143
1251.1140001006
1338
6284
200
text/css
Stylesheet
data
1424.112000037
1424.1720000282
0
37
200
image/gif
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/page-header-pixels.png?x44622
h2
1446.7470000964
1515.1790000964
29967
29299
200
image/png
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel-shadowed.png?x44622
h2
1447.3650001455
1527.647000039
31737
31069
200
image/png
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel-benefit.png?x44622
h2
1448.5460000578
1508.3739999682
15234
14566
200
image/png
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel.png?x44622
h2
1449.5570000727
1520.177999977
2515
1849
200
image/png
Image
https://fonts.gstatic.com/s/titilliumweb/v10/NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzY5abuWI.woff2
h2
1453.1849999912
1456.4290000126
13034
12276
200
font/woff2
Font
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fonts/ionicons.ttf?v=2.0.1&x44622
h2
1453.4790001344
1544.6760000195
110439
188508
200
application/x-font-ttf
Font
https://fonts.gstatic.com/s/titilliumweb/v10/NaPecZTIAOhVxoMyOr9n_E7fdMPmDaZRbrw.woff2
h2
1453.6680001765
1459.1159999836
13102
12344
200
font/woff2
Font
https://fonts.gstatic.com/s/titilliumweb/v10/NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzY5abuWI.woff2
h2
1454.4059999753
1458.6810001638
13281
12524
200
font/woff2
Font
https://fonts.gstatic.com/s/titilliumweb/v10/NaPFcZTIAOhVxoMyOr9n_E7fdMbepI5DYZycm2A2xQ.woff2
h2
1454.5289999805
1458.2060000394
14626
13868
200
font/woff2
Font
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/fonts/digital360.woff?x44622
h2
1454.9060000572
1543.6700000428
2093
2160
200
application/font-woff
Font
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/bg-footer.png?x44622
h2
1525.896999985
1577.872000169
9995
9328
200
image/png
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fontawesome/webfonts/fa-brands-400.woff2
h2
1527.4490001611
1603.0409999657
77439
76764
200
application/font-woff2
Font
https://fonts.gstatic.com/s/titilliumweb/v10/NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzY5abuWI.woff2
h2
1625.4720001016
1629.3190000579
12502
11744
200
font/woff2
Font
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/slick-carousel/ajax-loader.gif?x44622
h2
1672.5940001197
1702.009000117
4844
4178
200
image/gif
Image
data
1810.7610000297
1810.8400001656
0
82
200
image/webp
Image
https://cdnd360.it/networkdigital360/ND360_Logo_POS.svg
h2
1811.834000051
1966.3319999818
1849
3059
200
image/svg+xml
Image
https://media.digital360.it/wp-content/uploads/2021/05/29095758/logo-digital360-gradient.png.webp
h2
1915.4260000214
2043.050999986
6714
6166
200
image/webp
Image
https://www.digital360.it/wp-content/uploads/2021/06/bg-career-1.jpg.webp
h2
1915.6070000026
2143.441000022
56994
56534
200
image/webp
Image
https://media.digital360.it/wp-content/uploads/2021/05/29100037/Gabriele-Faggioli.jpg.webp
h2
1915.7269999851
2105.8040000498
10683
10134
200
image/webp
Image
https://media.digital360.it/wp-content/uploads/2021/05/29095914/Raffaello-Balocco.jpg.webp
h2
1916.119000176
2002.5840001181
5452
4904
200
image/webp
Image
https://media.digital360.it/wp-content/uploads/2021/07/14181954/AndreaRangonePresidenteDIGITAL360.jpg.webp
h2
2132.3730000295
2222.1200000495
14003
13454
200
image/webp
Image
https://www.digital360.it/wp-content/uploads/2021/06/Icona-Cosa-Facciamo.svg?x21018
h2
3399.6030001435
3545.9849999752
2067
4445
200
image/svg+xml
Image
https://media.digital360.it/wp-content/uploads/2021/05/29095807/people-icon.svg
h2
3400.2000000328
3583.7740001734
1764
2834
200
image/svg+xml
Image
https://media.digital360.it/wp-content/uploads/2021/05/29095803/media-icon.svg
h2
3400.3710001707
3452.5600001216
1651
3003
200
image/svg+xml
Image
https://www.digital360.it/wp-content/uploads/2021/06/work-with-us.png.webp
h2
3533.2290001679
3642.5240000244
2504
2046
200
image/webp
Image
https://media.digital360.it/wp-content/uploads/2021/05/29095805/investor-icon.svg
h2
3665.6590001658
3727.3020001594
1381
1628
200
image/svg+xml
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1233.116
14.063
1379.897
23.446
1403.406
60.011
1463.433
51.626
1530.712
28.205
1559.125
267.436
1826.907
63.849
1898.616
23.936
1922.608
13.304
1940.499
14.767
1955.309
22.03
1988.182
5.703
1994.06
16.566
2010.656
8.782
2230.193
170.897
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 1.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.6 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.129
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.2 s
The time taken for the primary content of the page to be rendered.

Opportunities

Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Digital360.it should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://digital360.it/
190
https://digital360.it/
150
https://www.digital360.it/
0

Diagnostics

Avoid an excessive DOM size — 894 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
894
Maximum DOM Depth
15
Maximum Child Elements
29

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fonts/ionicons.ttf?v=2.0.1&x44622
91.196999885142
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/fonts/digital360.woff?x44622
88.763999985531
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://media.digital360.it/wp-content/uploads/2021/05/29095758/logo-digital360-gradient.png.webp
https://www.digital360.it/wp-content/uploads/2021/06/work-with-us.png.webp
img
https://cdnd360.it/networkdigital360/ND360_Logo_POS.svg
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
87

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of digital360.it. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Digital360.it may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that digital360.it should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.6.0
Vue
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://digital360.it/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for digital360.it. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of digital360.it on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
73

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of digital360.it. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of digital360.it on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 72
Performance 29
Accessibility 81
Best Practices 87
SEO 89
Progressive Web App 75
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.digital360.it/
Updated: 28th July, 2021

1.22 seconds
First Contentful Paint (FCP)
89%
8%
3%

0.02 seconds
First Input Delay (FID)
88%
8%
4%

Simulate loading on mobile
29

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for digital360.it. This includes details about optimizing page load times which can result in a better user experience.

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Digital360.it should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Digital360.it should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Digital360.it should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 420 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.digital360.it/
418.21
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Digital360.it should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/882cf.js?x21018
54
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
48
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 704 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/02f41.css?x21018
118727
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fonts/ionicons.ttf?v=2.0.1&x44622
110439
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
82133
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fontawesome/webfonts/fa-brands-400.woff2
77439
https://www.digital360.it/wp-content/uploads/2021/06/bg-career-1.jpg.webp
56994
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
34906
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel-shadowed.png?x44622
31737
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/page-header-pixels.png?x44622
29967
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel-benefit.png?x44622
15234
https://www.digital360.it/
14823
Uses efficient cache policy on static assets — 1 resource found
Digital360.it can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://cdnd360.it/networkdigital360/ND360_Logo_POS.svg
259200000
1849
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Digital360.it should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 29 requests • 704 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
29
720971
Font
8
256516
Image
11
175984
Script
4
141706
Stylesheet
3
131165
Document
1
14823
Other
2
777
Media
0
0
Third-party
22
625528
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
67883
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.052232142857143
0.041517857142857
0.040602487963299
0.039301126169604
0.020821788699128
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 13 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
5577
792
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
5196
381
https://www.digital360.it/
698
330
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
3120
190
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
6456
109
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/02f41.css?x21018
4470
90
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
6565
87
https://www.digital360.it/
630
68
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
5070
65
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
5135
61
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
6652
56
https://www.digital360.it/
2047
54
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
6369
51
Avoid non-composited animations — 47 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
1
2

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://digital360.it/
http/1.1
0
231.03800002718
321
0
301
text/html
https://digital360.it/
http/1.1
231.5360000357
1029.3620000011
456
0
301
text/html
https://www.digital360.it/
h2
1029.8349999939
1447.0480000018
14823
76000
200
text/html
Document
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
h2
1455.8909999905
1536.6520000389
34906
100747
200
application/x-javascript
Script
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
h2
1456.1279999907
1554.1640000301
82133
288561
200
application/x-javascript
Script
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/882cf.js?x21018
h2
1456.3450000132
1534.9489999935
11938
40573
200
application/x-javascript
Script
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/e0515.js?x21018
h2
1456.6520000226
1534.0079999878
12729
39783
200
application/x-javascript
Script
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/a5ff7.css?x21018
h2
1456.8680000375
1547.8890000377
11100
80557
200
text/css
Stylesheet
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/02f41.css?x21018
h2
1457.1060000453
1618.775000039
118727
664311
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Titillium+Web%3Aital%2Cwght%400%2C300%3B0%2C400%3B0%2C600%3B0%2C700%3B1%2C300%3B1%2C400%3B1%2C600%3B1%2C700&display=swap&ver=1.0.6
h2
1464.7690000129
1484.1580000357
1338
6284
200
text/css
Stylesheet
data
1663.2940000272
1663.3370000054
0
37
200
image/gif
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/page-header-pixels.png?x44622
h2
1681.2539999955
1777.2070000065
29967
29299
200
image/png
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel-shadowed.png?x44622
h2
1681.7470000242
1733.9450000436
31737
31069
200
image/png
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel-benefit.png?x44622
h2
1682.6710000169
1760.4430000065
15234
14566
200
image/png
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/pixel.png?x44622
h2
1683.6820000317
1789.7039999953
2515
1849
200
image/png
Image
https://fonts.gstatic.com/s/titilliumweb/v10/NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzY5abuWI.woff2
h2
1688.5050000274
1692.4749999889
13282
12524
200
font/woff2
Font
https://fonts.gstatic.com/s/titilliumweb/v10/NaPFcZTIAOhVxoMyOr9n_E7fdMbepI5DYZycm2A2xQ.woff2
h2
1688.731000002
1693.1650000042
14625
13868
200
font/woff2
Font
https://fonts.gstatic.com/s/titilliumweb/v10/NaPecZTIAOhVxoMyOr9n_E7fdMPmDaZRbrw.woff2
h2
1688.9010000159
1692.8710000357
13102
12344
200
font/woff2
Font
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/fonts/digital360.woff?x44622
h2
1689.1879999894
1734.6970000071
2093
2160
200
application/font-woff
Font
https://fonts.gstatic.com/s/titilliumweb/v10/NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzY5abuWI.woff2
h2
1689.4709999906
1693.471000006
13034
12276
200
font/woff2
Font
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/images/bg-footer.png?x44622
h2
1740.2599999914
1771.2990000146
9995
9328
200
image/png
Image
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fontawesome/webfonts/fa-brands-400.woff2
h2
1741.4790000184
1850.3229999915
77439
76764
200
application/font-woff2
Font
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fonts/ionicons.ttf?v=2.0.1&x44622
h2
1741.8600000092
1855.447000009
110439
188508
200
application/x-font-ttf
Font
https://fonts.gstatic.com/s/titilliumweb/v10/NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzY5abuWI.woff2
h2
1823.4940000111
1827.5570000405
12502
11744
200
font/woff2
Font
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/slick-carousel/ajax-loader.gif?x44622
h2
1873.6710000085
1941.7560000438
4844
4178
200
image/gif
Image
data
2151.7459999886
2151.8030000152
0
82
200
image/webp
Image
https://cdnd360.it/networkdigital360/ND360_Logo_POS.svg
h2
2152.59100002
2222.4670000141
1849
3059
200
image/svg+xml
Image
https://media.digital360.it/wp-content/uploads/2021/05/29095758/logo-digital360-gradient.png.webp
h2
2293.6779999873
2598.273999989
6714
6166
200
image/webp
Image
https://www.digital360.it/wp-content/uploads/2021/06/bg-career-1.jpg.webp
h2
2294.1700000083
2803.2560000429
56994
56534
200
image/webp
Image
https://media.digital360.it/wp-content/uploads/2021/05/29100037/Gabriele-Faggioli.jpg.webp
h2
2636.164000025
2737.1900000144
10683
10134
200
image/webp
Image
https://media.digital360.it/wp-content/uploads/2021/05/29095914/Raffaello-Balocco.jpg.webp
h2
4004.6910000383
4112.8080000053
5452
4904
200
image/webp
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1458.726
8.906
1629.624
22.384
1652.054
47.586
1699.654
33.929
1746.343
27.152
1773.868
395.907
2170.129
82.546
2262.044
7.216
2269.479
32.682
2313.374
25.259
2338.648
17.858
2356.524
30.501
2387.048
27.26
2414.329
43.668
2463.744
5.802
2473.174
24.518
2813.12
190.427
5116.27
13.953
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Time to Interactive — 6.3 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.194
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 600 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Digital360.it should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Titillium+Web%3Aital%2Cwght%400%2C300%3B0%2C400%3B0%2C600%3B0%2C700%3B1%2C300%3B1%2C400%3B1%2C600%3B1%2C700&display=swap&ver=1.0.6
1338
780
Properly size images — Potential savings of 33 KiB
Images can slow down the page's load time. Digital360.it should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.digital360.it/wp-content/uploads/2021/06/bg-career-1.jpg.webp
56534
33709
Reduce unused JavaScript — Potential savings of 38 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
82133
39251

Diagnostics

Avoid an excessive DOM size — 957 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
957
Maximum DOM Depth
15
Maximum Child Elements
29
Reduce JavaScript execution time — 1.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/cb477.js?x21018
1898.208
967.82
30.708
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/818c0.js?x21018
1342.36
637.724
7.272
https://www.digital360.it/
1112.708
27.168
12.716
Unattributable
240.432
12.984
0.588
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/02f41.css?x21018
89.536
0
0

Metrics

First Contentful Paint — 4.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 6.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 6.8 s
The timing of the largest text or image that is painted.
Total Blocking Time — 1,190 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Max Potential First Input Delay — 790 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 4.2 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 8385 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Reduce unused CSS — Potential savings of 118 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Digital360.it should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/02f41.css?x21018
118727
109987
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/a5ff7.css?x21018
11100
11100
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Digital360.it should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://digital360.it/
630
https://digital360.it/
480
https://www.digital360.it/
0

Diagnostics

Minimize main-thread work — 4.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
1800.056
Script Evaluation
1655.712
Other
691.876
Rendering
307.776
Parse HTML & CSS
173.908
Script Parsing & Compilation
59.068
Garbage Collection
28.588
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/fonts/digital360.woff?x44622
45.509000017773
https://d2suf7dq4jlwt0.cloudfront.net/wp-content/themes/digital360/dist/css/vendor/fonts/ionicons.ttf?v=2.0.1&x44622
113.58699999982
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://media.digital360.it/wp-content/uploads/2021/05/29095758/logo-digital360-gradient.png.webp
https://cdnd360.it/networkdigital360/ND360_Logo_POS.svg
img
img
img
img
img
img
img
img
img
img
img
81

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of digital360.it. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Digital360.it may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that digital360.it should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.6.0
Vue
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://digital360.it/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
89

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for digital360.it. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of digital360.it on mobile screens.
Document uses legible font sizes — 95.83% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.newsletter-ir-list .think-tank-card .think-tank-card-content .think-tank-card-role, .think-tank-list .think-tank-card .think-tank-card-content .think-tank-card-role
2.99%
11px
#footer #footer-copyright .footer-block#footer-block-2 .footer-copyright-text
0.50%
10px
.gform_wrapper .gform_body .gform_fields .gfield .ginput_container.ginput_container_consent label
0.48%
11px
#footer #footer-copyright .footer-block#footer-block-2 .footer-menu-container-2 ul li a, #footer #footer-copyright .footer-block#footer-block-2 .footer-menu-container-2 ul li span
0.11%
10px
.slick-dots li button
0.07%
0px
0.02%
< 12px
95.83%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Mobile Friendly

Tap targets are not sized appropriately — 47% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
1
8x8
2
2
8x8
3
3
8x8
4
4
8x8
5
5
8x8
6
6
8x8
7
7
8x8
8
8
8x8
9
9
8x8
10
10
8x8
11
11
8x8
12
12
8x8
13
13
8x8
14
1
8x8
2
2
8x8
3

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
75

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of digital360.it. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of digital360.it on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 63.33.230.128
Continent: Europe
Country: Ireland
Ireland Flag
Region: Leinster
City: Dublin
Longitude: -6.2489
Latitude: 53.3331
Currencies: EUR
Languages: English
Irish

Web Hosting Provider

Name IP Address
Amazon Data Services Ireland Limited
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.digital360.it
Issued By: R3
Valid From: 14th January, 2022
Valid To: 14th April, 2022
Subject: CN = www.digital360.it
Hash: dbbda371
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x034AC6A94DFE0268306358D7BB8765E9DB5D
Serial Number (Hex): 034AC6A94DFE0268306358D7BB8765E9DB5D
Valid From: 14th January, 2024
Valid To: 14th April, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Jan 14 18:29:09.511 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B3:B0:AF:01:08:40:09:D2:61:F5:96:
2D:D0:F9:C5:19:99:99:95:C9:F8:0B:AA:E2:57:D3:DD:
0A:E2:55:59:3F:02:20:23:F2:7E:D8:84:5F:09:66:DE:
AE:EC:54:67:F3:10:37:69:44:5C:C5:19:94:A0:7B:63:
63:34:56:86:C1:C9:04
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Jan 14 18:29:09.998 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:31:BF:EE:F8:53:67:8A:9D:43:7F:F3:AA:
0F:33:0C:EF:F4:80:FA:FB:D3:F7:AF:3A:57:BF:07:C1:
08:60:86:93:02:21:00:A6:E6:F5:19:7C:F3:5C:50:AA:
89:C4:F0:B5:8C:AA:1F:7D:C0:07:D2:87:F1:47:0F:63:
95:73:8F:92:24:DB:B6
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:p4i.it
DNS:www.digital360.it
DNS:www.p4i.it
DNS:digital360.it
Technical

DNS Lookup

A Records

Host IP Address Class TTL
digital360.it. 63.33.230.128 IN 14400

NS Records

Host Nameserver Class TTL
digital360.it. ns-1160.awsdns-17.org. IN 21600
digital360.it. ns-1795.awsdns-32.co.uk. IN 21600
digital360.it. ns-29.awsdns-03.com. IN 21600
digital360.it. ns-683.awsdns-21.net. IN 21600

MX Records

Priority Host Server Class TTL
10 digital360.it. digital360-it.mail.protection.outlook.com. IN 14400

SOA Records

Domain Name Primary NS Responsible Email TTL
digital360.it. ns-1795.awsdns-32.co.uk. awsdns-hostmaster.amazon.com. 900

TXT Records

Host Value Class TTL
digital360.it. google-site-verification=8NbWQ2QccKhopTMvLBxonp3DNEVH7BMbnqVCM3AYPTY IN 14400
digital360.it. google-site-verification=PO4nqEqBk84KnY9uGPUhLQyimeWrChLl8vGmUCjpUtw IN 14400
digital360.it. have-i-been-pwned-verification=4600f31a353f006a3c6505a23d414446 IN 14400
digital360.it. ms=ms94659653 IN 14400
digital360.it. v=DKIM1 IN 14400
digital360.it. v=spf1 IN 14400

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 24th January, 2022
Server: Apache/2.4.29 (Ubuntu)
Cache-Control: max-age=107, public, must-revalidate, proxy-revalidate, public, must-revalidate, proxy-revalidate
Expires: 24th January, 2022
Content-Type: text/html; charset=UTF-8
Upgrade: h2
Connection: Upgrade
Last-Modified: 24th January, 2022
ETag: "12219-5d65198706ae9"
Accept-Ranges: bytes
Content-Length: 74265
Vary: Accept-Encoding,Cookie
Referrer-Policy: no-referrer-when-downgrade
Access-Control-Allow-Origin: *
Pragma: public
Link: <https://d2suf7dq4jlwt0.cloudfront.net/wp-content/cache/minify/60579.css?x80321>; rel=preload; as=style

Whois Lookup

Created:
Changed:
Expires:
Status: clientDeleteProhibited
Nameservers: ns-1160.awsdns-17.org
ns-1795.awsdns-32.co.uk
ns-29.awsdns-03.com
ns-683.awsdns-21.net
Full Whois:
*********************************************************************
* Please note that the following result could be a subgroup of *
* the data contained in the database. *
* *
* Additional information can be visualized at: *
* http://web-whois.nic.it *
* Privacy Information: http://web-whois.nic.it/privacy *
*********************************************************************

Domain: digital360.it
Status: clientDeleteProhibited
Signed: no
Created: 2012-12-17 16:25:38
Last Update: 2021-12-07 00:56:31
Expire Date: 2022-11-21

Registrant
Organization: ICT AND STRATEGY S.R.L.
Address: Via Simone Schiaffino, 25
MILANO
20158
MI
IT
Created: 2020-11-21 00:55:18
Last Update: 2020-11-21 00:55:17

Admin Contact
Name: hidden
Organization: hidden

Technical Contacts
Name: hidden
Organization: hidden

Registrar
Organization: OVH
Name: OVH-REG
Web: http://www.ovh.com/welcome
DNSSEC: no


Nameservers
ns-1795.awsdns-32.co.uk
ns-29.awsdns-03.com
ns-1160.awsdns-17.org
ns-683.awsdns-21.net


Nameservers

Name IP Address
ns-1160.awsdns-17.org 205.251.196.136
ns-1795.awsdns-32.co.uk 205.251.199.3
ns-29.awsdns-03.com 205.251.192.29
ns-683.awsdns-21.net 205.251.194.171
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$980 USD 1/5
0/5
$865 USD 1/5