2.2 sec in total
289 ms
1.8 sec
104 ms
Welcome to portail.unige.ch homepage info - get ready to check Portail Unige best content for Switzerland right away, or after learning these important things about portail.unige.ch
Visit portail.unige.chWe analyzed Portail.unige.ch page load time and found that the first response time was 289 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
portail.unige.ch performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value2.5 s
89/100
25%
Value4.4 s
75/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.5 s
98/100
10%
289 ms
406 ms
100 ms
95 ms
189 ms
Our browser made a total of 16 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original Portail.unige.ch, 88% (14 requests) were made to Idp.unige.ch. The less responsive or slowest element that took the longest time to load (406 ms) belongs to the original domain Portail.unige.ch.
Page size can be reduced by 2.9 kB (62%)
4.7 kB
1.8 kB
In fact, the total size of Portail.unige.ch main page is 4.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 4.7 kB which makes up the majority of the site volume.
Potential reduce by 2.9 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 2.9 kB or 62% of the original size.
Number of requests can be reduced by 7 (54%)
13
6
The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portail Unige. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
portail.unige.ch
289 ms
portail.unige.ch
406 ms
SSO;jsessionid=EEA116EBC0B657ECB990E3202F75640E
100 ms
main.css
95 ms
uni-logo-trans.gif
189 ms
switchaai-logo.png
281 ms
fond.png
170 ms
topleft.gif
170 ms
topcenter.gif
262 ms
topright.gif
264 ms
middleleft.gif
264 ms
middleright.gif
280 ms
bottomleft_prod.gif
282 ms
bottomcenter_prod.gif
282 ms
bottomright_prod.gif
353 ms
3pRed.png
353 ms
portail.unige.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
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
portail.unige.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
portail.unige.ch SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portail.unige.ch can be misinterpreted by Google and other search engines. Our service has detected that English 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 Portail.unige.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.
portail.unige.ch
Open Graph description is not detected on the main page of Portail Unige. 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: