5.5 sec in total
299 ms
4.7 sec
414 ms
Click here to check amazing GS1 content for Switzerland. Otherwise, check out these important facts you probably never knew about gs1.ch
Die GS1 Standards bilden branchenübergreifend die globale Sprache für effiziente und sichere Geschäftsprozesse.
Visit gs1.chWe analyzed Gs1.ch page load time and found that the first response time was 299 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
gs1.ch performance score
name
value
score
weighting
Value30.4 s
0/100
10%
Value36.2 s
0/100
25%
Value30.4 s
0/100
10%
Value1,070 ms
24/100
30%
Value0
100/100
15%
Value37.6 s
0/100
10%
299 ms
822 ms
804 ms
296 ms
317 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 94% of them (60 requests) were addressed to the original Gs1.ch, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Gs1.ch.
Page size can be reduced by 2.6 MB (50%)
5.2 MB
2.6 MB
In fact, the total size of Gs1.ch main page is 5.2 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. 35% of websites need less resources to load. Javascripts take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 61.5 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 61.5 kB or 80% of the original size.
Potential reduce by 161.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. GS1 images are well optimized though.
Potential reduce by 2.0 MB
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 2.0 MB or 71% of the original size.
Potential reduce by 314.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. Gs1.ch needs all CSS files to be minified and compressed as it can save up to 314.6 kB or 84% of the original size.
Number of requests can be reduced by 35 (58%)
60
25
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GS1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
gs1.ch
299 ms
www.gs1.ch
822 ms
home
804 ms
jquery.fancybox.css
296 ms
default.css
317 ms
Telerik.Web.UI.WebResource.axd
409 ms
idangerous.swiper.css
333 ms
bootstrap.min.css
725 ms
bootstrap-responsive.min.css
432 ms
sitefinityreset.css
399 ms
layout.css
817 ms
gs1styles.css
437 ms
WebResource.axd
523 ms
Telerik.Web.UI.WebResource.axd
907 ms
ScriptResource.axd
626 ms
Telerik.Web.UI.WebResource.axd
642 ms
ScriptResource.axd
620 ms
ScriptResource.axd
733 ms
Telerik.Web.UI.WebResource.axd
749 ms
mobilyblocks.js
572 ms
jquery.fancybox.pack.js
647 ms
xok1vll.js
193 ms
bootstrap.min.js
646 ms
jquery.fittext.js
669 ms
jQuery.browser.mobile.js
674 ms
idangerous.swiper.min.js
786 ms
GS1_Niveau0_Parsing.js
786 ms
gs1_switzerland_154x75.png
150 ms
search-black.png
151 ms
more-black.png
151 ms
allgemein-1x1.png
311 ms
wir-ueber-uns.jpg
400 ms
mitglied-werden.jpg
398 ms
gs1system_dunkel-1x1.png
398 ms
csc-hell_1x1.png
399 ms
bildung_hell-1x1.png
397 ms
events_hell-1x1.png
399 ms
medien.jpg
594 ms
support.jpg
642 ms
gs1_ziehen-um_kachel_engl.jpg
1745 ms
news---magazin.jpg
609 ms
netzwerke.jpg
512 ms
gesundheitswesen.jpg
625 ms
ich-brauche-einen-barcode_allgemein.jpg
657 ms
suchebox
591 ms
bg_header.png
597 ms
langbtnDE-black.png
597 ms
langbtnEN-black.png
604 ms
langbtnIT-black.png
620 ms
langbtnFR-black.png
692 ms
searchbtn-black.png
701 ms
kontaktbtn-black.png
704 ms
morebtn-black.png
706 ms
loginbtn-black.png
722 ms
logoutbtn-blackorange.png
795 ms
backbtn-black.png
805 ms
bg-crumbs.png
808 ms
bg_footer.png
784 ms
analytics.js
202 ms
collect
13 ms
collect
55 ms
Telerik.Web.UI.WebResource.axd
506 ms
Telerik.Web.UI.WebResource.axd
518 ms
Telerik.Web.UI.WebResource.axd
1112 ms
gs1.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
[role]s do not have all required [aria-*] attributes
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
gs1.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
Page has valid source maps
gs1.ch 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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gs1.ch can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Gs1.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.
gs1.ch
Open Graph description is not detected on the main page of GS1. 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: