10.5 sec in total
1.6 sec
8.4 sec
601 ms
Welcome to brolliet.ch homepage info - get ready to check Brolliet best content for Switzerland right away, or after learning these important things about brolliet.ch
En savoir plus sur l'entité Brolliet du groupe Emeria.
Visit brolliet.chWe analyzed Brolliet.ch page load time and found that the first response time was 1.6 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
brolliet.ch performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value14.2 s
0/100
25%
Value8.8 s
16/100
10%
Value2,140 ms
6/100
30%
Value0.057
98/100
15%
Value13.0 s
13/100
10%
1553 ms
248 ms
169 ms
168 ms
167 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 97% of them (84 requests) were addressed to the original Brolliet.ch, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Js-agent.newrelic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Brolliet.ch.
Page size can be reduced by 526.1 kB (33%)
1.6 MB
1.1 MB
In fact, the total size of Brolliet.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. 50% of websites need less resources to load. Images take 896.3 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.8 kB or 80% of the original size.
Potential reduce by 25.9 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. Brolliet images are well optimized though.
Potential reduce by 344.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 344.3 kB or 67% of the original size.
Potential reduce by 115.1 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. Brolliet.ch needs all CSS files to be minified and compressed as it can save up to 115.1 kB or 81% of the original size.
Number of requests can be reduced by 39 (46%)
85
46
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brolliet. 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 10 to 1 for CSS and as a result speed up the page load time.
www.brolliet.ch
1553 ms
jquery.js
248 ms
language-selector.css
169 ms
styles.css
168 ms
reset.css
167 ms
globle.css
166 ms
style.css
309 ms
flexslider.css
326 ms
owl.carousel.css
328 ms
magnific-popup.css
329 ms
jquery.js
409 ms
jquery-migrate.min.js
406 ms
script-minified.js
471 ms
jquery.flexslider-minified.js
488 ms
jquery-ui-1.10.3.custom.min.js
492 ms
jquery-ui-1.10.3.custom.min.js
491 ms
Autolinker.min.js
567 ms
jquery.magnific-popup.js
572 ms
customInput.jquery.js
629 ms
print.css
649 ms
jquery.validate.min.js
586 ms
jquery.form.min.js
512 ms
scripts.js
589 ms
navigation.js
593 ms
skip-link-focus-fix.js
650 ms
respond.min.js
670 ms
jquery.meanmenu-minified.js
674 ms
sitepress.js
675 ms
bootstrap-dropdown.js
748 ms
wp-emoji-release.min.js
622 ms
style.css
652 ms
analytics.js
33 ms
menu-title.png
181 ms
logo.png
168 ms
child-nav-divider.gif
177 ms
timthumb.php
174 ms
timthumb.php
176 ms
timthumb.php
190 ms
timthumb.php
368 ms
nav-divider.jpg
331 ms
timthumb.php
339 ms
timthumb.php
349 ms
timthumb.php
359 ms
timthumb.php
356 ms
timthumb.php
530 ms
timthumb.php
526 ms
timthumb.php
517 ms
timthumb.php
563 ms
timthumb.php
547 ms
timthumb.php
555 ms
timthumb.php
681 ms
timthumb.php
691 ms
timthumb.php
696 ms
timthumb.php
720 ms
timthumb.php
721 ms
timthumb.php
729 ms
timthumb.php
849 ms
child-nav-bg.png
862 ms
caption-bg.png
873 ms
timthumb.php
1058 ms
timthumb.php
961 ms
timthumb.php
969 ms
timthumb.php
1089 ms
timthumb.php
1282 ms
cote-prestige-light.png
1035 ms
timthumb.php
1292 ms
timthumb.php
1312 ms
timthumb.php
1504 ms
collect
25 ms
raleway-medium-webfont.svg
1224 ms
raleway-medium-webfont.woff
1169 ms
timthumb.php
1504 ms
timthumb.php
1439 ms
timthumb.php
1471 ms
timthumb.php
1398 ms
timthumb.php
1321 ms
timthumb.php
1492 ms
block-sd-tp.png
1399 ms
icon-history.png
1435 ms
icon-inno.png
1462 ms
icon-env.png
1448 ms
icon-ln.png
1326 ms
icon-mail.png
1385 ms
footer.png
1423 ms
logo_uspi.png
1430 ms
bg_direction_nav.png
1426 ms
nr-892.min.js
16 ms
brolliet.ch accessibility score
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
Links do not have a discernible name
brolliet.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
brolliet.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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brolliet.ch can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Brolliet.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.
brolliet.ch
Open Graph data is detected on the main page of Brolliet. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: