5.7 sec in total
434 ms
4.1 sec
1.1 sec
Welcome to ipi.ch homepage info - get ready to check Ipi best content for Switzerland right away, or after learning these important things about ipi.ch
Das Eidgenössische Institut für Geistiges Eigentum (IGE) in Bern ist die zentrale Anlaufstelle des Bundes für alle Fragen zu Patenten, Marken, Herkunftsbezeichnungen, Designschutz und Urheberrecht.
Visit ipi.chWe analyzed Ipi.ch page load time and found that the first response time was 434 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 75% of websites can load faster.
ipi.ch performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value7.5 s
4/100
25%
Value8.4 s
19/100
10%
Value160 ms
93/100
30%
Value0.001
100/100
15%
Value9.9 s
27/100
10%
434 ms
321 ms
215 ms
964 ms
995 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ipi.ch, 63% (42 requests) were made to Ige.ch and 21% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Ige.ch.
Page size can be reduced by 131.9 kB (9%)
1.5 MB
1.3 MB
In fact, the total size of Ipi.ch main page is 1.5 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 70.7 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 70.7 kB or 82% of the original size.
Potential reduce by 61.0 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. Ipi images are well optimized though.
Potential reduce by 36 B
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 36 B or 28% of the original size.
Potential reduce by 153 B
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. Ipi.ch needs all CSS files to be minified and compressed as it can save up to 153 B or 21% of the original size.
Number of requests can be reduced by 27 (54%)
50
23
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ipi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
ipi.ch
434 ms
321 ms
slimbox2.css
215 ms
merged-ae1b9f38cdfab508da582d57b7247a32-db2fa20049c5de18dcf7fad6997a68e5.css
964 ms
merged-835ec1ac71684c36bd975b73afc5939c-ca629fecec873edb285f8a5943878986.js
995 ms
merged-e42f19d81a1216cce62fec146860b96e-382c51de33eceb743dc8e9da4d7bb90d.js
646 ms
loadMoreNewsArticles.js
328 ms
css
24 ms
startpage-new-2023.css
326 ms
merged-4807e6869e766fd1881e6618cc050504-7e57664b3ea5d4c4b154aef36b9713b2.js
224 ms
merged-e1528e165b5aac82cc73b6b478d03d95-c469c0c77044b2f69b30afb8764ce06f.js
755 ms
slimbox2.js
333 ms
showonlyfirst.js
335 ms
rotateimages.js
444 ms
323 ms
IGE_Logo_neu.svg
219 ms
Etwas_schuetzen_Uhr_568x247px.png
135 ms
Einstiegskachel_Cuboro.jpg
534 ms
Einstiegskachel_Flauder.jpg
534 ms
Einstiegskachel_Kuenzli.jpg
637 ms
Einstiegskachel_Sutter_AG.jpg
532 ms
Einstiegskachel_Swibox_de.jpg
958 ms
Was_ist_geistiges_Eigentum_368x160px.png
326 ms
Teaser_Patentrecherchen_ipsearch_368x160px.png
437 ms
IGE_Teaser_Datenbanken_368x160px.png
546 ms
csm_founded_Bild_1_e9d183e96d.jpg
642 ms
csm_enten-patent_836fff31d6.jpg
641 ms
csm_spennemann_portraet2_404979e1ab.png
746 ms
csm_Mathieu_Evelyne_IGE-IPI-4MB_20dd5f28b9.jpg
655 ms
Bild_LSR_resized.jpg
955 ms
Teaser_Patentgesetzrevision_368_200_2.png
852 ms
Mitarbeitende_Reiseverkehr_Zuerich_BAZG_resizedKopie.jpg
1063 ms
Teaser_Swissness_gross_389x242px.png
764 ms
x.svg
855 ms
x_hover.svg
873 ms
xing.svg
961 ms
xing_hover_ige.svg
965 ms
linkedin-square.svg
983 ms
linkedin-square_hover_ige.svg
1063 ms
rss.svg
1065 ms
rss_hover_ige.svg
1069 ms
arrow.png
946 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff
20 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo.woff
26 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo.woff
41 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo.woff
49 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
51 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
50 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
50 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
50 ms
line-awesome.svg
1208 ms
line-awesome.woff
1146 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rl.woff
47 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rl.woff
50 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rl.woff
69 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rl.woff
70 ms
semantic.min.css
34 ms
css
15 ms
css
27 ms
ige.css
103 ms
jquery.min.js
77 ms
iframeResizer.contentWindow.min.js
243 ms
ige.js
205 ms
css
27 ms
S6u9w4BMUTPHh6UVSwiPHw.woff
5 ms
S6uyw4BMUTPHjx4wWA.woff
4 ms
merged-b8a4b10a0efaa7d8e6584c4765f5a097-e8c561e210caabdfc562abaddd187d25.css
112 ms
ipi.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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role] values are not valid
[aria-*] attributes are not valid or misspelled
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
Image elements do not have [alt] attributes
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
ipi.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
Browser errors were logged to the console
Page has valid source maps
ipi.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Ipi.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 Ipi.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.
ipi.ch
Open Graph description is not detected on the main page of Ipi. 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: