5.8 sec in total
Visit billag.ch now to see the best up-to-date BILLAG content for Switzerland and also check out these interesting facts you probably never knew about billag.chVisit billag.ch
We analyzed Billag.ch page load time and found that the first response time was 1.3 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
billag.ch performance score
Our browser made a total of 14 requests to load all elements on the main page. We found that 79% of them (11 requests) were addressed to the original Billag.ch, 14% (2 requests) were made to Fast.fonts.com and 7% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Billag.ch.
Page size can be reduced by 839.8 kB (52%)
In fact, the total size of Billag.ch main page is 1.6 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. 15% of websites need less resources to load. CSS take 857.8 kB which makes up the majority of the site volume.
Potential reduce by 30.8 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 30.8 kB or 69% of the original size.
Potential reduce by 33.2 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. BILLAG images are well optimized though.
Potential reduce by 42.8 kB
Potential reduce by 733.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. Billag.ch needs all CSS files to be minified and compressed as it can save up to 733.0 kB or 85% of the original size.
Number of requests can be reduced by 3 (25%)
billag.ch accessibility score
These are opportunities to improve the legibility of your content.
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.
<html> element does not have a [lang] attribute
billag.ch best practices score
Trust and Safety
Does not use HTTPS
Ensure CSP is effective against XSS attacks
Serves images with low resolution
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
billag.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
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/).
Document uses legible font sizes
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Billag.ch can be misinterpreted by Google and other search engines. Our service has detected that German 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 Billag.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.
Open Graph description is not detected on the main page of BILLAG. 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: