2.8 sec in total
515 ms
2 sec
268 ms
Welcome to otto.to.it homepage info - get ready to check Otto To best content right away, or after learning these important things about otto.to.it
Web, UI/UX, video, multimedia, publishing
Visit otto.to.itWe analyzed Otto.to.it page load time and found that the first response time was 515 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
otto.to.it performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value5.3 s
21/100
25%
Value11.1 s
6/100
10%
Value710 ms
42/100
30%
Value0.032
100/100
15%
Value9.6 s
29/100
10%
515 ms
206 ms
200 ms
198 ms
200 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 73% of them (27 requests) were addressed to the original Otto.to.it, 14% (5 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (598 ms) belongs to the original domain Otto.to.it.
Page size can be reduced by 452.5 kB (49%)
928.2 kB
475.7 kB
In fact, the total size of Otto.to.it main page is 928.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 387.0 kB which makes up the majority of the site volume.
Potential reduce by 12.9 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 2.4 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 12.9 kB or 72% of the original size.
Potential reduce by 2.8 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Otto To images are well optimized though.
Potential reduce by 271.7 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 271.7 kB or 70% of the original size.
Potential reduce by 165.0 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Otto.to.it needs all CSS files to be minified and compressed as it can save up to 165.0 kB or 85% of the original size.
Number of requests can be reduced by 18 (60%)
30
12
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otto To. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
otto.to.it
515 ms
styles.css
206 ms
datepicker_jqui.css
200 ms
slimbox.css
198 ms
home.css
200 ms
menu_mainMenu.css
198 ms
searchSite.css
203 ms
blog_blog.css
293 ms
news_news.css
294 ms
mootools-1.4.0-yc.js
598 ms
modernizr.js
292 ms
gino-min.js
303 ms
searchSite.js
298 ms
news.js
388 ms
wordevents.js
389 ms
navigator.js
390 ms
css
30 ms
b9dc20087087e05cff111b8c657e52e3.js
173 ms
ga.js
94 ms
search.png
123 ms
right_arrow.png
124 ms
home_tiles.jpg
590 ms
icoRSS_black.png
124 ms
thumb_cover_330px.1.jpg
203 ms
thumb_cope_vauda_sito_2.png
284 ms
thumb_citterio.jpg
284 ms
thumb_itinerario.jpg
286 ms
thumb_tablet_oddone.jpg
288 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
38 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
37 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
45 ms
fontawesome-webfont.woff
302 ms
7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf
38 ms
__utm.gif
37 ms
jquery.min.js
47 ms
slimbox.js
105 ms
otto.to.it accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Form elements do not have associated labels
Links do not have a discernible name
otto.to.it best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
otto.to.it SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otto.to.it can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Otto.to.it main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
otto.to.it
Open Graph description is not detected on the main page of Otto To. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: