3.4 sec in total
326 ms
2.7 sec
370 ms
Click here to check amazing Regent content for Germany. Otherwise, check out these important facts you probably never knew about regent.ch
People light our way. Seit unseren Anfängen vor über hundert Jahren waren Menschen die treibende Kraft bei allem, was wir tun. Die Menschen, die planen. Die Menschen, die installieren. Die Menschen, d...
Visit regent.chWe analyzed Regent.ch page load time and found that the first response time was 326 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
regent.ch performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value9.4 s
0/100
25%
Value6.8 s
34/100
10%
Value460 ms
62/100
30%
Value0.282
43/100
15%
Value15.7 s
6/100
10%
326 ms
165 ms
105 ms
316 ms
206 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 97% of them (69 requests) were addressed to the original Regent.ch, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Regent.ch.
Page size can be reduced by 235.7 kB (19%)
1.3 MB
1.0 MB
In fact, the total size of Regent.ch main page is 1.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. 20% of websites need less resources to load. Images take 932.0 kB which makes up the majority of the site volume.
Potential reduce by 24.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 24.3 kB or 82% of the original size.
Potential reduce by 501 B
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. Regent images are well optimized though.
Potential reduce by 151.0 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 151.0 kB or 66% of the original size.
Potential reduce by 59.9 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. Regent.ch needs all CSS files to be minified and compressed as it can save up to 59.9 kB or 85% of the original size.
Number of requests can be reduced by 13 (19%)
68
55
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Regent. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
regent.ch
326 ms
en.html
165 ms
google-sitesearch.css
105 ms
style.css
316 ms
jquery.customcombo.css
206 ms
jquery.fancybox.css
210 ms
jquery-1.7.2.min.js
346 ms
jquery.cookie.js
228 ms
NetvClientDetect.js
230 ms
jquery.ThreeDots.min.js
306 ms
regent.js
311 ms
jquery.customcombo.js
368 ms
jquery.fancybox.pack.js
370 ms
plugins.js
407 ms
pi2.js
444 ms
analytics.js
37 ms
spot.jpg
216 ms
logo_inverted.png
105 ms
logo.png
111 ms
icons.png
113 ms
a87ea84752.jpg
119 ms
068f33e911.jpg
114 ms
72d0ad6ebd.jpg
214 ms
clear.gif
227 ms
1ba13a3ff6.jpg
231 ms
5a79b7da58.jpg
227 ms
b00a7792f7.jpg
237 ms
4a0bade405.jpg
319 ms
c07d2687db.jpg
321 ms
94a9904e6e.jpg
338 ms
f83a3327a1.jpg
438 ms
35385b8316.jpg
348 ms
722711c373.jpg
353 ms
00c90a8898.jpg
424 ms
f6f731f327.jpg
422 ms
cde0669be3.jpg
450 ms
019b281b49.jpg
460 ms
b59c684f8b.jpg
465 ms
ade2c7caed.jpg
628 ms
48e47c9ea4.jpg
531 ms
f18992ebe6.jpg
542 ms
647109477c.jpg
560 ms
cf34a0e69a.jpg
571 ms
63c04b6ae3.jpg
578 ms
fd46640e4a.jpg
635 ms
88c1649103.jpg
646 ms
3421cd3369.jpg
671 ms
b1eee8ae6d.jpg
1021 ms
b24fa54275.jpg
807 ms
70080b16d7.jpg
1044 ms
f9d26b873a.jpg
941 ms
49827e5bb5.jpg
833 ms
collect
12 ms
SeccaStdWeb-Regular.woff
798 ms
ajax.tx_netvregproducts_pi2.php
817 ms
803434386b.jpg
1077 ms
71cb851e57.jpg
1008 ms
ee504bba67.jpg
1040 ms
1374674ac0.jpg
857 ms
teaser_bg.png
921 ms
21e97d2915.jpg
1031 ms
2921501ff0.jpg
951 ms
86b4c3d8ae.jpg
1113 ms
629e89a3a8.jpg
1015 ms
689f51ae3d.jpg
1062 ms
d4a8b61288.jpg
966 ms
9ca0f4c30b.jpg
956 ms
ce3d303c6f.jpg
1018 ms
icon_vimeo.gif
1011 ms
icon_you_tube.gif
968 ms
print.css
106 ms
regent.ch accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
regent.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
regent.ch SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Regent.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 Regent.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.
regent.ch
Open Graph description is not detected on the main page of Regent. 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: