7.3 sec in total
478 ms
4.3 sec
2.5 sec
Click here to check amazing Freepatent content for Russia. Otherwise, check out these important facts you probably never knew about freepatent.ru
Патентный поиск в библиотеке патентов и изобретений, зарегистрированных в РФ, патентные исследования. На сайте вы можете найти патент и бесплатно скачать официальную публикацию патента в формате PDF
Visit freepatent.ruWe analyzed Freepatent.ru page load time and found that the first response time was 478 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
freepatent.ru performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value3.4 s
67/100
25%
Value10.2 s
8/100
10%
Value1,150 ms
22/100
30%
Value0.324
35/100
15%
Value18.5 s
3/100
10%
478 ms
769 ms
268 ms
11 ms
7 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 73% of them (80 requests) were addressed to the original Freepatent.ru, 5% (5 requests) were made to Pagead2.googlesyndication.com and 5% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Freepatent.ru.
Page size can be reduced by 379.8 kB (53%)
716.5 kB
336.7 kB
In fact, the total size of Freepatent.ru main page is 716.5 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. 55% of websites need less resources to load. Javascripts take 324.9 kB which makes up the majority of the site volume.
Potential reduce by 248.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 248.8 kB or 81% of the original size.
Potential reduce by 7.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. Freepatent images are well optimized though.
Potential reduce by 113.0 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 113.0 kB or 35% of the original size.
Potential reduce by 10.9 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. Freepatent.ru needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 76% of the original size.
Number of requests can be reduced by 33 (31%)
107
74
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freepatent. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
freepatent.ru
478 ms
www.freepatent.ru
769 ms
style.css
268 ms
share.js
11 ms
adsbygoogle.js
7 ms
logo.png
294 ms
jquery-1.4.2.min.js
196 ms
jquery.fancybox-1.3.1.pack.js
203 ms
all.js
21 ms
top-bg.jpg
182 ms
2540093-9-s_prew.gif
356 ms
2540092-3-s2_prew.gif
436 ms
2540091-s2_prew.gif
356 ms
2540089-8-s_prew.gif
356 ms
945.gif
484 ms
946.gif
484 ms
948.gif
630 ms
2540087-6-s_prew.gif
612 ms
2540085-3.gif
611 ms
2540082.gif
704 ms
2540081-s2_prew.gif
621 ms
2540080-9-s_prew.gif
743 ms
8242.gif
900 ms
2540079-10.gif
857 ms
2540077-53-s_prew.gif
766 ms
2540076-6-s_prew.gif
764 ms
2540075-4-s_prew.gif
829 ms
2540074-691-s_prew.gif
1009 ms
8801.gif
1061 ms
2540074-692.gif
1026 ms
2540072-s2_prew.gif
1090 ms
8804.gif
1161 ms
947.gif
1201 ms
2540070-6.gif
1274 ms
2540069-2.gif
1293 ms
2540067-8-s2_prew.jpg
1187 ms
2540066-s2_prew.gif
1223 ms
2540065-9-s2_prew.jpg
1291 ms
2540064-s2_prew.gif
1448 ms
2540062-s2_prew.jpg
1493 ms
2540061-s2_prew.jpg
1490 ms
2540058-s2_prew.gif
1395 ms
2540055-s2_prew.gif
1411 ms
jquery.min.js
189 ms
ca-pub-5205483873115932.js
203 ms
zrt_lookup.html
176 ms
show_ads_impl.js
140 ms
pfsquaresanspro-light.ttf
1653 ms
pfhandbookpro-regular.ttf
1505 ms
2540053-s2_prew.jpg
1513 ms
ads
275 ms
suggest.js
85 ms
opensearch.js
122 ms
osd.js
52 ms
ads
257 ms
ga.js
46 ms
watch.js
172 ms
b-share-icon.png
54 ms
ads
258 ms
__utm.gif
42 ms
2540052-s2_prew.gif
1229 ms
2540051-s2_prew.gif
1402 ms
2540050-s2_prew.gif
1405 ms
watch.js
742 ms
2540049-s2_prew.gif
1486 ms
2540047-s2_prew.gif
1338 ms
2540046-s2_prew.gif
1341 ms
m_js_controller.js
35 ms
abg.js
57 ms
favicon
76 ms
favicon
75 ms
googlelogo_color_112x36dp.png
75 ms
nessie_icon_tiamat_white.png
47 ms
s
40 ms
x_button_blue2.png
21 ms
2540045-s2_prew.gif
1310 ms
2540044-s2_prew.gif
1410 ms
2540043-2-s2_prew.gif
1463 ms
8722.gif
1505 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
7 ms
2540041-s2_prew.gif
1265 ms
2540040-s2_prew.gif
1364 ms
2540039-s2_prew.gif
1255 ms
2540038-s2_prew.gif
1464 ms
2540037-s2_prew.jpg
1464 ms
2540036-s2_prew.gif
1439 ms
2540035-s2_prew.gif
1447 ms
2540034-s2_prew.jpg
1358 ms
2540033-s2_prew.gif
1372 ms
2540032-s2_prew.gif
1306 ms
2540029-6-s2_prew.gif
1335 ms
2540027-s2_prew.gif
1399 ms
advert.gif
91 ms
2540026-3-s2_prew.gif
1295 ms
2540025-s2_prew.gif
1431 ms
2540024-s2_prew.jpg
1274 ms
2540019-s2_prew.gif
1390 ms
2540012-2-s_prew.gif
1265 ms
2540011-s2_prew.jpg
1456 ms
1
91 ms
2540004-s2_prew.gif
1350 ms
2540003-13-s2_prew.gif
1393 ms
2540002-s2_prew.gif
1379 ms
26812653
91 ms
2540001-s2_prew.jpg
1272 ms
2540000-15-s2_prew.gif
1436 ms
2539997-10.gif
1434 ms
blank.gif
1366 ms
top.png
1282 ms
foot-bg.jpg
1197 ms
freepatent.ru 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
freepatent.ru 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
Issues were logged in the Issues panel in Chrome Devtools
freepatent.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freepatent.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Freepatent.ru 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.
freepatent.ru
Open Graph description is not detected on the main page of Freepatent. 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: