4.2 sec in total
331 ms
3.5 sec
289 ms
Visit wipo.int now to see the best up-to-date WIPO content for China and also check out these interesting facts you probably never knew about wipo.int
The world’s number one source for global intellectual property (patents, industrial designs, copyright, trademarks etc.) information, resources, and services.
Visit wipo.intWe analyzed Wipo.int page load time and found that the first response time was 331 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
wipo.int performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value25.0 s
0/100
25%
Value13.8 s
1/100
10%
Value10,390 ms
0/100
30%
Value0.001
100/100
15%
Value27.1 s
0/100
10%
331 ms
314 ms
1025 ms
241 ms
242 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 94% of them (32 requests) were addressed to the original Wipo.int, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Wipo.int.
Page size can be reduced by 477.5 kB (48%)
988.1 kB
510.6 kB
In fact, the total size of Wipo.int main page is 988.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 613.5 kB which makes up the majority of the site volume.
Potential reduce by 21.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 21.8 kB or 76% of the original size.
Potential reduce by 203.6 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. Obviously, WIPO needs image optimization as it can save up to 203.6 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 124.9 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 124.9 kB or 63% of the original size.
Potential reduce by 127.2 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. Wipo.int needs all CSS files to be minified and compressed as it can save up to 127.2 kB or 86% of the original size.
Number of requests can be reduced by 8 (26%)
31
23
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WIPO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
wipo.int
331 ms
index.html
314 ms
styles.css
1025 ms
ss-standard.css
241 ms
modernizr-2.6.2-min.js
242 ms
jquery-min.js
826 ms
dbInfo.js
458 ms
plugins.js
646 ms
main.js
359 ms
ss-standard.js
421 ms
wipo-portal.js
418 ms
patentscope.js
361 ms
theme-blue-body.png
274 ms
header-logo-wipo.png
290 ms
theme-blue-banner-logo-wipox2x.png
278 ms
gdcm_600_200.jpg
1490 ms
promo.png
271 ms
promo-pct.png
582 ms
promo-madrid.png
923 ms
promo-hague.png
831 ms
wipo_conf_hall.jpg
513 ms
ss-standard.woff
632 ms
wipo_wipi_launch_2015_140.jpg
857 ms
pdf.gif
807 ms
ip_dev_conference_2016_300.jpg
1244 ms
contentinfo.png
1061 ms
selfx2x.png
1064 ms
social.png
1111 ms
ga.js
5 ms
topic_upcoming.xml
1119 ms
ocms_workshops.xml
1270 ms
patentscope.html
1281 ms
__utm.gif
1313 ms
__utm.gif
12 ms
wipo.int 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-hidden="true"] elements contain focusable descendents
[role]s are not contained by their required parent element
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
wipo.int 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
Missing source maps for large first-party JavaScript
wipo.int 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
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wipo.int can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wipo.int 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.
wipo.int
Open Graph description is not detected on the main page of WIPO. 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: