3.7 sec in total
994 ms
2.4 sec
298 ms
Click here to check amazing M 4 Ti content for Switzerland. Otherwise, check out these important facts you probably never knew about m4.ti.ch
Repubblica e Cantone Ticino - www.ti.ch è il sito ufficiale dell'Amministrazione cantonale ticinese: un servizio d'informazione per il cittadino e per il personale dello Stato
Visit m4.ti.chWe analyzed M4.ti.ch page load time and found that the first response time was 994 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
m4.ti.ch performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value20.3 s
0/100
25%
Value20.5 s
0/100
10%
Value13,480 ms
0/100
30%
Value0.186
66/100
15%
Value30.4 s
0/100
10%
994 ms
202 ms
206 ms
305 ms
308 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 95% of them (42 requests) were addressed to the original M4.ti.ch, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (994 ms) belongs to the original domain M4.ti.ch.
Page size can be reduced by 1.2 MB (54%)
2.3 MB
1.1 MB
In fact, the total size of M4.ti.ch main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 29.7 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 4.2 kB, which is 11% 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 29.7 kB or 80% of the original size.
Potential reduce by 28.6 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. M 4 Ti images are well optimized though.
Potential reduce by 931.3 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 931.3 kB or 80% of the original size.
Potential reduce by 259.6 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. M4.ti.ch needs all CSS files to be minified and compressed as it can save up to 259.6 kB or 81% of the original size.
Number of requests can be reduced by 30 (70%)
43
13
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M 4 Ti. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
m4.ti.ch
994 ms
stylesheet_e92edc110c.css
202 ms
jquery.fancybox.css
206 ms
font-awesome.min.css
305 ms
style.css
308 ms
joyride-2.1.css
208 ms
owl.carousel.css
221 ms
Mobile.css
301 ms
fontac.css
306 ms
bootstrap.min.css
512 ms
mymobile.css
546 ms
javascript_0b12553063.js
404 ms
daterangepicker.css
406 ms
mobile.css
407 ms
jquery.js
627 ms
bootstrap.min.js
412 ms
jquery.colorbox-min.js
414 ms
bootstrap-select.min.js
415 ms
bootstrap-datepicker.js
557 ms
owl.carousel.min.js
558 ms
select2.min.js
654 ms
d3.js
736 ms
readmore.js
592 ms
jquery.joyride-2.1.js
619 ms
jsGenerale.js
622 ms
tichmobile_menus.js
667 ms
jquery.mousewheel-3.0.6.pack.js
730 ms
jquery.fancybox.js
732 ms
javascript_61d7382bd3.js
731 ms
moment.js
765 ms
daterangepicker.js
779 ms
js.js
834 ms
analytics.js
43 ms
logo_ti.png
361 ms
stemma_ti.png
303 ms
slider-modelli_080316.png
512 ms
slider_chiusura_040316.png
713 ms
Truffa-online.png
573 ms
pp_osservatorio_080216.png
605 ms
slider_cpa_070116_.png
809 ms
aef05e22-e1d4-4e59-bc2e-a71c13c26cca.woff
486 ms
collect
14 ms
fontawesome-webfont.woff
659 ms
fontawesome-webfont.woff
754 ms
m4.ti.ch accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
m4.ti.ch 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
m4.ti.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M4.ti.ch can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that M4.ti.ch 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.
m4.ti.ch
Open Graph description is not detected on the main page of M 4 Ti. 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: