4.5 sec in total
1.1 sec
2.9 sec
429 ms
Click here to check amazing E Patent Search content for Japan. Otherwise, check out these important facts you probably never knew about e-patentsearch.net
e-Patentは株式会社イーパテント運営の特許情報を中心とした知財情報調査・分析に関するポータルサイトです。 現在は下
Visit e-patentsearch.netWe analyzed E-patentsearch.net page load time and found that the first response time was 1.1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
e-patentsearch.net performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value6.5 s
9/100
25%
Value9.3 s
13/100
10%
Value110 ms
98/100
30%
Value0.109
87/100
15%
Value10.8 s
22/100
10%
1124 ms
663 ms
344 ms
17 ms
8 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 49% of them (21 requests) were addressed to the original E-patentsearch.net, 14% (6 requests) were made to Google.com and 9% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain E-patentsearch.net.
Page size can be reduced by 36.7 kB (17%)
214.7 kB
178.0 kB
In fact, the total size of E-patentsearch.net main page is 214.7 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. 30% of websites need less resources to load. Images take 138.5 kB which makes up the majority of the site volume.
Potential reduce by 22.6 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 22.6 kB or 77% of the original size.
Potential reduce by 1.3 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. E Patent Search images are well optimized though.
Potential reduce by 420 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. This website has mostly compressed JavaScripts.
Potential reduce by 12.3 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. E-patentsearch.net needs all CSS files to be minified and compressed as it can save up to 12.3 kB or 84% of the original size.
Number of requests can be reduced by 30 (73%)
41
11
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Patent Search. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
e-patentsearch.net
1124 ms
common.css
663 ms
divlink.js
344 ms
jsapi
17 ms
show_ads.js
8 ms
13 ms
default+en.css
3 ms
default+en.I.js
5 ms
logo01.png
343 ms
body_background01.png
1026 ms
listmark01.png
177 ms
sankaku.png
333 ms
listmark02.png
360 ms
listmark03.png
371 ms
listmark04.png
379 ms
listmark05.png
499 ms
listmark06.png
507 ms
listmark07.png
537 ms
listmark08.png
547 ms
listmark09.png
565 ms
listmark10.png
665 ms
top_mark01.png
678 ms
top_mark02.png
714 ms
top_date01.png
728 ms
nozaki_avatar-48x48.jpg
751 ms
top_mark03.png
830 ms
zrt_lookup.html
41 ms
show_ads_impl.js
40 ms
ads
210 ms
osd.js
48 ms
ga.js
16 ms
__utm.gif
20 ms
m_js_controller.js
28 ms
abg.js
51 ms
favicon
44 ms
googlelogo_color_112x36dp.png
44 ms
nessie_icon_tiamat_white.png
35 ms
s
21 ms
x_button_blue2.png
9 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
6 ms
__utm.gif
4 ms
Gfeeds
402 ms
ui
35 ms
e-patentsearch.net 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
Image elements do not have [alt] attributes
e-patentsearch.net 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
e-patentsearch.net 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-patentsearch.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that E-patentsearch.net 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.
e-patentsearch.net
Open Graph description is not detected on the main page of E Patent Search. 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: