1.8 sec in total
287 ms
1.3 sec
258 ms
Visit guinnessworldrecords.in now to see the best up-to-date Guinness World Records content and also check out these interesting facts you probably never knew about guinnessworldrecords.in
The Guinness World Records official site with ultimate record-breaking facts & achievements. Do you want to set a world record? Are you Officially Amazing?
Visit guinnessworldrecords.inWe analyzed Guinnessworldrecords.in page load time and found that the first response time was 287 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
guinnessworldrecords.in performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value17.5 s
0/100
25%
Value16.6 s
0/100
10%
Value4,070 ms
1/100
30%
Value0.208
60/100
15%
Value25.7 s
0/100
10%
287 ms
28 ms
109 ms
97 ms
301 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Guinnessworldrecords.in, 53% (28 requests) were made to Guinnessworldrecords.com and 6% (3 requests) were made to Lf16-tiktok-web.tiktokcdn-us.com. The less responsive or slowest element that took the longest time to load (654 ms) relates to the external source Guinnessworldrecords.com.
Page size can be reduced by 232.5 kB (31%)
739.9 kB
507.4 kB
In fact, the total size of Guinnessworldrecords.in main page is 739.9 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. 65% of websites need less resources to load. Images take 351.6 kB which makes up the majority of the site volume.
Potential reduce by 57.9 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 57.9 kB or 75% of the original size.
Potential reduce by 164.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. Obviously, Guinness World Records needs image optimization as it can save up to 164.3 kB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 9.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 529 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. Guinnessworldrecords.in has all CSS files already compressed.
Number of requests can be reduced by 19 (40%)
47
28
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guinness World 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 20 to 1 for JavaScripts and as a result speed up the page load time.
guinnessworldrecords.in
287 ms
www.guinnessworldrecords.com
28 ms
www.guinnessworldrecords.com
109 ms
gppstub.js
97 ms
boise.js
301 ms
abilene.js
340 ms
tulsa.js
370 ms
main.rtl.min.css
49 ms
ccpaplus.js
297 ms
modernizr.js
91 ms
jquery.js
186 ms
language.js
90 ms
scripts.min.js
205 ms
embed.js
201 ms
widgets.js
333 ms
v.js
272 ms
ezoic.png
280 ms
logo.png
118 ms
cubes.png
190 ms
GWR_load.gif
190 ms
product.png
212 ms
business.png
212 ms
news.png
211 ms
about.png
249 ms
gwr_kids_link.jpg
654 ms
GPSD-thumb1_tcm25-769479.jpg
278 ms
close-up-of-italy-lifting-euro-2020-trophy_tcm25-770033.jpg
252 ms
smallest-playing-cards-held-in-hand_tcm25-770085.jpg
252 ms
man-riding-tallest-bicylce_tcm25-770017.jpg
252 ms
Nikki-the-oldest-mandrill_tcm25-770080.jpg
281 ms
The-Beast-rollercoaster_tcm25-769919.jpg
311 ms
close-up-of-scene-from-the-wizard-of-oz_tcm25-770021.jpg
278 ms
g.jpg
277 ms
B2B%20Online%20Records%20Banner_tcm25-619559.jpg
312 ms
footer-strapline.png
310 ms
rubik-regular-webfont.woff
227 ms
gwr.ttf
226 ms
rubik-medium-webfont.woff
227 ms
embed_v1.0.12.js
197 ms
fbevents.js
103 ms
bat.js
146 ms
analytics.js
134 ms
insight.min.js
135 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
119 ms
embed_lib_v1.0.12.css
15 ms
embed_lib_v1.0.12.js
22 ms
collect
36 ms
settings
79 ms
collect
36 ms
js
75 ms
ga-audiences
73 ms
logo_pride.png
133 ms
pd.js
18 ms
guinnessworldrecords.in 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
guinnessworldrecords.in 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
Page has valid source maps
guinnessworldrecords.in 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
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 Guinnessworldrecords.in 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 Guinnessworldrecords.in 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.
guinnessworldrecords.in
Open Graph data is detected on the main page of Guinness World Records. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: