10.6 sec in total
1.1 sec
8.8 sec
705 ms
Click here to check amazing Guinness Records content for Russia. Otherwise, check out these important facts you probably never knew about guinness-records.info
Книга рекордов Гиннеса: самые необычные рекорды
Visit guinness-records.infoWe analyzed Guinness-records.info page load time and found that the first response time was 1.1 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
guinness-records.info performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value5.0 s
27/100
25%
Value5.4 s
57/100
10%
Value330 ms
76/100
30%
Value0.267
46/100
15%
Value4.8 s
79/100
10%
1061 ms
24 ms
86 ms
254 ms
169 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 65% of them (75 requests) were addressed to the original Guinness-records.info, 6% (7 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Guinness-records.info.
Page size can be reduced by 569.8 kB (27%)
2.1 MB
1.5 MB
In fact, the total size of Guinness-records.info main page is 2.1 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 69.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. This page needs HTML code to be minified as it can gain 9.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 69.8 kB or 84% of the original size.
Potential reduce by 53.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. Guinness Records images are well optimized though.
Potential reduce by 341.1 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 341.1 kB or 68% of the original size.
Potential reduce by 105.8 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. Guinness-records.info needs all CSS files to be minified and compressed as it can save up to 105.8 kB or 68% of the original size.
Number of requests can be reduced by 43 (43%)
100
57
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guinness Records. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
guinness-records.info
1061 ms
css
24 ms
style.css
86 ms
dashicons.min.css
254 ms
desktop_style.css
169 ms
form_style.css
170 ms
shortcodes.css
173 ms
font-awesome.min.css
171 ms
css
49 ms
style.css
174 ms
media-queries.css
254 ms
css
48 ms
wzslider.css
254 ms
custom.css
255 ms
lightbox.min.ru_RU.css
255 ms
jquery.js
342 ms
jquery-migrate.min.js
336 ms
front_end_script.js
337 ms
cntctfrm.js
337 ms
loader.js
123 ms
vertical-m.css
337 ms
b3c4df5b509f.js
170 ms
zp.js
691 ms
jquery.mmenu.min.all.js
334 ms
jquery.carouFredSel-6.2.1-packed.js
462 ms
flickity.pkgd.min.js
519 ms
jquery.fitvids.js
459 ms
superfish.min.js
461 ms
tabs.js
462 ms
functions.js
464 ms
galleria.js
607 ms
wzslider.js
538 ms
jquery.touchwipe.min.js
537 ms
jquery.lightbox.min.js
533 ms
wp-embed.min.js
515 ms
foobar.js
201 ms
wp-emoji-release.min.js
595 ms
1_1_FFFFFFFF_EFEFEFFF_0_visits
296 ms
header.png
224 ms
search-icon.png
222 ms
003-12-612x450.jpg
606 ms
001-12-675x450.jpg
608 ms
001-11.jpg
607 ms
003-7.jpg
607 ms
002-6.jpg
604 ms
001-5-300x450.jpg
604 ms
004-1.jpg
634 ms
002-1-674x450.jpg
635 ms
001-4-630x450.jpg
634 ms
001-464x450.jpg
635 ms
1-640x394.jpg
693 ms
001-13-75x50.jpg
633 ms
001-12-75x50.jpg
705 ms
001-11-75x50.jpg
705 ms
003-7-640x394.jpg
818 ms
002-6-75x50.jpg
712 ms
003-1-75x50.jpg
711 ms
001-6-75x50.jpg
777 ms
003-12-640x400.jpg
872 ms
001-16-75x50.jpg
815 ms
004-4-75x50.jpg
817 ms
jquery.js
90 ms
229 ms
001-75x50.jpg
759 ms
1-225x145.jpg
803 ms
001-225x145.jpg
816 ms
003-12-225x145.jpg
816 ms
001-16-225x145.jpg
817 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
76 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
76 ms
Uxzkqj-MIMWle-XP2pDNAA.ttf
106 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
107 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
102 ms
n3IzcUkIerri6e9sz7DgbqCWcynf_cDxXwCLxiixG1c.ttf
102 ms
GkRQHvchMkUIVL72Zh3gyw.ttf
72 ms
003-11-225x145.jpg
812 ms
hit
515 ms
watch.js
202 ms
001-14-225x145.jpg
816 ms
001-13-225x145.jpg
821 ms
001-12-225x145.jpg
823 ms
001-11-225x145.jpg
824 ms
003-7-225x145.jpg
826 ms
675269.js
436 ms
1-90x75.jpg
749 ms
001-90x75.jpg
815 ms
003-12-90x75.jpg
5820 ms
001-16-90x75.jpg
764 ms
watch.js
501 ms
hit
139 ms
003-11-90x75.jpg
447 ms
001-14-90x75.jpg
449 ms
001-13-90x75.jpg
449 ms
001-4-620x400.jpg
5852 ms
2-1-640x360.jpg
532 ms
6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==
10 ms
002-8-640x400.jpg
608 ms
675269.html
96 ms
001-2-640x366.jpg
587 ms
jQuery.js
105 ms
advert.gif
90 ms
jsonp.php
99 ms
100x100.gif
257 ms
100x100.gif
263 ms
100x100.gif
266 ms
100x100.gif
275 ms
1
91 ms
23414332
92 ms
impression.html
309 ms
sync
319 ms
extra.js
310 ms
pixel
18 ms
388 ms
pixel
16 ms
match
93 ms
guinness-records.info accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
guinness-records.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
guinness-records.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guinness-records.info can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Russian language. Our system also found out that Guinness-records.info 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.
guinness-records.info
Open Graph description is not detected on the main page of Guinness Records. 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: