Tools & Wizards About Us
ti.ch screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

ti.ch

Stato e organizzazione - Repubblica e Cantone Ticino

Page Load Speed

6.5 sec in total

First Response

1 sec

Resources Loaded

5.4 sec

Page Rendered

106 ms

ti.ch screenshot

About Website

Welcome to ti.ch homepage info - get ready to check Ti best content for Switzerland right away, or after learning these important things about 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 ti.ch

Key Findings

We analyzed Ti.ch page load time and found that the first response time was 1 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ti.ch performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.196

63/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

stato-e-organizzazione

1030 ms

ruxitagentjs_ICA7NVfqrux_10287240325103108.js

425 ms

bfe1d76c3a.css

323 ms

styles.css

324 ms

Basic.css

438 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ti.ch, 3% (2 requests) were made to Statistiche.ti.ch and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Www4.ti.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 102.1 kB (13%)

Content Size

806.2 kB

After Optimization

704.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ti.ch main page is 806.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. 50% of websites need less resources to load. Images take 690.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 74.9 kB

  • Original 94.2 kB
  • After minification 89.5 kB
  • After compression 19.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 74.9 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 27.2 kB

  • Original 690.5 kB
  • After minification 663.3 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. Ti images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 22 B

  • Original 21.4 kB
  • After minification 21.4 kB
  • After compression 21.4 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 40 (60%)

Requests Now

67

After Optimization

27

  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 22 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

stato-e-organizzazione

stato-e-organizzazione

1030 ms

ruxitagentjs_ICA7NVfqrux_10287240325103108.js

ruxitagentjs_ICA7NVfqrux_10287240325103108.js

425 ms

bfe1d76c3a.css

bfe1d76c3a.css

323 ms

styles.css

styles.css

324 ms

Basic.css

Basic.css

438 ms

bootstrap.min.css

bootstrap.min.css

537 ms

styles.css

styles.css

964 ms

font-awesome.min.css

font-awesome.min.css

541 ms

style.css

style.css

543 ms

bootstrap-datetimepicker.min.css

bootstrap-datetimepicker.min.css

532 ms

bootstrap-select.min.css

bootstrap-select.min.css

544 ms

owl.carousel.css

owl.carousel.css

641 ms

datepicker.css

datepicker.css

645 ms

select2.min.css

select2.min.css

644 ms

fontac.css

fontac.css

644 ms

ekko-lightbox.css

ekko-lightbox.css

647 ms

4911dd4315.css

4911dd4315.css

749 ms

Attualita.css

Attualita.css

750 ms

daterangepicker.css

daterangepicker.css

752 ms

e9e07c5ca0.js

e9e07c5ca0.js

752 ms

css.css

css.css

753 ms

jquery.js

jquery.js

986 ms

bootstrap.min.js

bootstrap.min.js

857 ms

jsGenerale.js

jsGenerale.js

1189 ms

jQuery.highlighter.js

jQuery.highlighter.js

859 ms

moment.js

moment.js

985 ms

bootstrap-select.min.js

bootstrap-select.min.js

984 ms

bootstrap-datepicker.js

bootstrap-datepicker.js

984 ms

owl.carousel.min.js

owl.carousel.min.js

1070 ms

select2.min.js

select2.min.js

1076 ms

d3.js

d3.js

1296 ms

readmore.js

readmore.js

1078 ms

ekko-lightbox.js

ekko-lightbox.js

1080 ms

jquery.datetimepicker.min.js

jquery.datetimepicker.min.js

1180 ms

parsley.min.js

parsley.min.js

1186 ms

Tabs.min.js

Tabs.min.js

1188 ms

Form.min.js

Form.min.js

1188 ms

captcha.js

captcha.js

972 ms

daterangepicker.js

daterangepicker.js

1133 ms

bootstrap-theme.css

bootstrap-theme.css

767 ms

gtm.js

gtm.js

173 ms

ti-ch.png

ti-ch.png

226 ms

Vitta.jpg

Vitta.jpg

228 ms

Gobbi.jpg

Gobbi.jpg

226 ms

Zali.jpg

Zali.jpg

228 ms

Carobbio-Guscetti.jpg

Carobbio-Guscetti.jpg

226 ms

DeRosa.jpg

DeRosa.jpg

224 ms

Coduri.jpg

Coduri.jpg

333 ms

governo.gif

governo.gif

342 ms

gray.gif

gray.gif

333 ms

tribunale-federale.gif

tribunale-federale.gif

343 ms

palazzo-federale.gif

palazzo-federale.gif

342 ms

diritti-politici.gif

diritti-politici.gif

341 ms

pp_teatro_forum.jpg

pp_teatro_forum.jpg

440 ms

pp-elezioni-comunali-2017_d.png

pp-elezioni-comunali-2017_d.png

652 ms

porte_aperte_circolazione.jpg

porte_aperte_circolazione.jpg

554 ms

Biodivesita_pp.jpg

Biodivesita_pp.jpg

763 ms

Il_piatto_equilibrato.png

Il_piatto_equilibrato.png

766 ms

csm_Lingua_facile_a9804c5898.png

csm_Lingua_facile_a9804c5898.png

450 ms

csm_Elezioni_19bb5aae1a.png

csm_Elezioni_19bb5aae1a.png

547 ms

MedicoCantonale.png

MedicoCantonale.png

558 ms

resto.png

resto.png

656 ms

RaccoltaLeggi.png

RaccoltaLeggi.png

660 ms

polizia_e_territorio.png

polizia_e_territorio.png

665 ms

ti_footer.png

ti_footer.png

758 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

760 ms

aef05e22-e1d4-4e59-bc2e-a71c13c26cca.woff

aef05e22-e1d4-4e59-bc2e-a71c13c26cca.woff

659 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

667 ms

matomo.js

matomo.js

235 ms

matomo.php

matomo.php

175 ms

stampa.css

stampa.css

109 ms

Accessibility Review

ti.ch accessibility score

72

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

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

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

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

High

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

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ti.ch best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ti.ch SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.

Social Sharing Optimization

ti.ch

Open Graph description is not detected on the main page of 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: