Tools & Wizards About Us
guinnessworldrecords.jp screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

guinnessworldrecords.jp

ギネスワールドレコーズ公式サイト | ギネス世界記録

Page Load Speed

1.4 sec in total

First Response

14 ms

Resources Loaded

919 ms

Page Rendered

439 ms

guinnessworldrecords.jp screenshot

About Website

Click here to check amazing Guinnessworldrecords content for Japan. Otherwise, check out these important facts you probably never knew about guinnessworldrecords.jp

ギネスワールドレコーズの数々の記録や、記録挑戦の方法などを紹介しています。また、企業・団体による記録挑戦のご提案なども行っています。

Visit guinnessworldrecords.jp

Key Findings

We analyzed Guinnessworldrecords.jp page load time and found that the first response time was 14 ms and then it took 1.4 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.

Performance Metrics

guinnessworldrecords.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.193

64/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

guinnessworldrecords.jp

14 ms

guinnessworldrecords.jp

20 ms

main.rtl.min.css

7 ms

modernizr.js

42 ms

jquery.js

173 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 64% of them (28 requests) were addressed to the original Guinnessworldrecords.jp, 7% (3 requests) were made to Lf16-tiktok-web.tiktokcdn-us.com and 5% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (782 ms) belongs to the original domain Guinnessworldrecords.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 354.8 kB (18%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Guinnessworldrecords.jp main page is 2.0 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 83.1 kB

  • Original 97.0 kB
  • After minification 66.0 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 31.0 kB, which is 32% 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 83.1 kB or 86% of the original size.

Image Optimization

-15%

Potential reduce by 234.5 kB

  • Original 1.6 MB
  • After minification 1.4 MB

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, Guinnessworldrecords needs image optimization as it can save up to 234.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 36.3 kB

  • Original 228.9 kB
  • After minification 228.7 kB
  • After compression 192.6 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 36.3 kB or 16% of the original size.

CSS Optimization

-1%

Potential reduce by 806 B

  • Original 72.8 kB
  • After minification 72.8 kB
  • After compression 72.0 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. Guinnessworldrecords.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (26%)

Requests Now

38

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guinnessworldrecords. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

guinnessworldrecords.jp

guinnessworldrecords.jp

14 ms

guinnessworldrecords.jp

guinnessworldrecords.jp

20 ms

main.rtl.min.css

main.rtl.min.css

7 ms

modernizr.js

modernizr.js

42 ms

jquery.js

jquery.js

173 ms

language.js

language.js

187 ms

scripts.min.js

scripts.min.js

188 ms

embed.js

embed.js

345 ms

widgets.js

widgets.js

382 ms

logo.png

logo.png

297 ms

cubes.png

cubes.png

595 ms

GWR_load.gif

GWR_load.gif

297 ms

product.png

product.png

571 ms

business.png

business.png

782 ms

news.png

news.png

648 ms

about.png

about.png

661 ms

SHumRbt-thumb1_tcm30-768772.jpg

SHumRbt-thumb1_tcm30-768772.jpg

305 ms

RobotCube-thumb_tcm30-769583.jpg

RobotCube-thumb_tcm30-769583.jpg

310 ms

24h-pullup-thumb_tcm30-768451.jpg

24h-pullup-thumb_tcm30-768451.jpg

318 ms

Animate-thumb1_tcm30-768684.jpg

Animate-thumb1_tcm30-768684.jpg

338 ms

Andrea-Lanfri-sitting-on-a-rock_tcm30-764258.jpg

Andrea-Lanfri-sitting-on-a-rock_tcm30-764258.jpg

343 ms

Sophia-Hayden-wearing-45-sweaters_tcm30-764897.jpg

Sophia-Hayden-wearing-45-sweaters_tcm30-764897.jpg

370 ms

mark-mckinley-close-up_tcm30-741104.jpg

mark-mckinley-close-up_tcm30-741104.jpg

384 ms

Peter-smiling-with-68-matches-in-his-nostrils_tcm30-764775.jpg

Peter-smiling-with-68-matches-in-his-nostrils_tcm30-764775.jpg

385 ms

g.jpg

g.jpg

386 ms

B2B%20Online%20Records%20Banner_tcm30-619559.jpg

B2B%20Online%20Records%20Banner_tcm30-619559.jpg

405 ms

footer-strapline.png

footer-strapline.png

406 ms

rubik-regular-webfont.woff

rubik-regular-webfont.woff

278 ms

gwr.ttf

gwr.ttf

308 ms

rubik-medium-webfont.woff

rubik-medium-webfont.woff

322 ms

analytics.js

analytics.js

63 ms

insight.min.js

insight.min.js

79 ms

embed_v1.0.12.js

embed_v1.0.12.js

39 ms

collect

collect

35 ms

insight_tag_errors.gif

insight_tag_errors.gif

210 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

93 ms

collect

collect

84 ms

js

js

132 ms

embed_lib_v1.0.12.css

embed_lib_v1.0.12.css

4 ms

embed_lib_v1.0.12.js

embed_lib_v1.0.12.js

20 ms

230 ms

settings

settings

101 ms

ga-audiences

ga-audiences

92 ms

pd.js

pd.js

25 ms

Accessibility Review

guinnessworldrecords.jp accessibility score

92

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

guinnessworldrecords.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

guinnessworldrecords.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guinnessworldrecords.jp 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 Guinnessworldrecords.jp 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.

Social Sharing Optimization

guinnessworldrecords.jp

Open Graph data is detected on the main page of Guinnessworldrecords. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: