Tools & Wizards About Us
rotten-g.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

rotten-g.com

ROTTENGRAFFTY OFFICIAL WEB SITE

Page Load Speed

6.2 sec in total

First Response

601 ms

Resources Loaded

4.8 sec

Page Rendered

757 ms

rotten-g.com screenshot

About Website

Visit rotten-g.com now to see the best up-to-date Rotten G content for Turkey and also check out these interesting facts you probably never knew about rotten-g.com

古都のドブネズミ、ROTTENGRAFFTYオフィシャルサイト

Visit rotten-g.com

Key Findings

We analyzed Rotten-g.com page load time and found that the first response time was 601 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

rotten-g.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value33.2 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value3,020 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value28.6 s

0/100

10%

Network Requests Diagram

rotten-g.com

601 ms

rotten-g.com

833 ms

gtm.js

99 ms

js

80 ms

reset.css

189 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 48% of them (59 requests) were addressed to the original Rotten-g.com, 15% (18 requests) were made to Platform.twitter.com and 11% (14 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Rotten-g.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 201.3 kB (3%)

Content Size

5.8 MB

After Optimization

5.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rotten-g.com main page is 5.8 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. Only a small number of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 45.8 kB

  • Original 56.6 kB
  • After minification 51.0 kB
  • After compression 10.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 45.8 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 135.8 kB

  • Original 5.2 MB
  • After minification 5.0 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. Rotten G images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 11.7 kB

  • Original 453.2 kB
  • After minification 451.0 kB
  • After compression 441.5 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.

CSS Optimization

-9%

Potential reduce by 7.9 kB

  • Original 85.8 kB
  • After minification 84.5 kB
  • After compression 77.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. Rotten-g.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 72 (62%)

Requests Now

117

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rotten-g.com

rotten-g.com

601 ms

rotten-g.com

rotten-g.com

833 ms

gtm.js

gtm.js

99 ms

js

js

80 ms

reset.css

reset.css

189 ms

base.css

base.css

376 ms

layout.css

layout.css

545 ms

slick.css

slick.css

549 ms

slick-theme.css

slick-theme.css

563 ms

colorbox.css

colorbox.css

574 ms

module.css

module.css

581 ms

contents.css

contents.css

586 ms

css

css

64 ms

css

css

95 ms

e23a7d2c57.js

e23a7d2c57.js

96 ms

api.js

api.js

68 ms

js

js

96 ms

widgets.js

widgets.js

134 ms

jquery.min.js

jquery.min.js

49 ms

modernizr.min.js

modernizr.min.js

59 ms

jquery.easing.min.js

jquery.easing.min.js

67 ms

jquery.crea.smoothscroll.js

jquery.crea.smoothscroll.js

775 ms

jquery.jmap.min.js

jquery.jmap.min.js

775 ms

jquery.cookie.js

jquery.cookie.js

819 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

819 ms

jquery.imagemapster.min.js

jquery.imagemapster.min.js

819 ms

init.js

init.js

820 ms

contents.js

contents.js

1095 ms

slick.min.js

slick.min.js

1095 ms

jquery.parallax-1.1.3.js

jquery.parallax-1.1.3.js

1193 ms

jquery.scrollTo-1.4.2-min.js

jquery.scrollTo-1.4.2-min.js

1195 ms

e23a7d2c57.css

e23a7d2c57.css

60 ms

font-awesome-css.min.css

font-awesome-css.min.css

13 ms

recaptcha__en.js

recaptcha__en.js

115 ms

artistPhoto231227.jpg

artistPhoto231227.jpg

1392 ms

icon_x_white.png

icon_x_white.png

605 ms

amazonMusic.png

amazonMusic.png

1008 ms

spotify.png

spotify.png

629 ms

lineMusic.png

lineMusic.png

758 ms

appleMusic.png

appleMusic.png

1200 ms

googlePlayMusic.png

googlePlayMusic.png

1012 ms

awa.png

awa.png

1369 ms

topMainLogo_25th.png

topMainLogo_25th.png

1170 ms

topMainLogoThunder.png

topMainLogoThunder.png

1011 ms

logo_25th.png

logo_25th.png

1190 ms

610ClubLogo.png

610ClubLogo.png

1202 ms

393.jpg

393.jpg

2103 ms

391.jpg

391.jpg

2095 ms

392.jpg

392.jpg

2156 ms

386.jpg

386.jpg

1986 ms

377.jpg

377.jpg

1730 ms

380.jpg

380.jpg

1592 ms

378.jpg

378.jpg

1776 ms

379.jpg

379.jpg

2091 ms

bigNavMoreArrow.png

bigNavMoreArrow.png

1968 ms

footerBnr610Club.jpg

footerBnr610Club.jpg

2158 ms

footerBnrLineAccount.jpg

footerBnrLineAccount.jpg

2166 ms

footerBnrLineStamp_second.jpg

footerBnrLineStamp_second.jpg

2271 ms

footerBnrKue_2024.jpg

footerBnrKue_2024.jpg

2277 ms

footerBnrSubscription.jpg

footerBnrSubscription.jpg

2289 ms

sdk.js

sdk.js

98 ms

_DuIDSgj2Kc

_DuIDSgj2Kc

177 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

101 ms

totopMountain.png

totopMountain.png

2235 ms

totopArrow.png

totopArrow.png

2239 ms

sdk.js

sdk.js

42 ms

topMask.png

topMask.png

2204 ms

mainImg_231227.jpg

mainImg_231227.jpg

2299 ms

backImgMask.png

backImgMask.png

2303 ms

contentsBgSchedule.jpg

contentsBgSchedule.jpg

2322 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

26 ms

base.js

base.js

56 ms

ad_status.js

ad_status.js

218 ms

contentsBgDiscography.jpg

contentsBgDiscography.jpg

2105 ms

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

156 ms

embed.js

embed.js

115 ms

contentsBgBiography.jpg

contentsBgBiography.jpg

2010 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

250 ms

contentsBgGoods.jpg

contentsBgGoods.jpg

1953 ms

footerBnrArrow.png

footerBnrArrow.png

2035 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

135 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

138 ms

ajax-loader.gif

ajax-loader.gif

2018 ms

page.php

page.php

143 ms

slick.woff

slick.woff

2039 ms

id

id

129 ms

slideArrow.png

slideArrow.png

1974 ms

Create

Create

41 ms

e0qhfylH8yR.css

e0qhfylH8yR.css

35 ms

DaPJf3IFK7Z.js

DaPJf3IFK7Z.js

125 ms

qQ7H5jmx4pn.js

qQ7H5jmx4pn.js

38 ms

oOOj7ijtZAT.js

oOOj7ijtZAT.js

35 ms

RLVuU6AS6qq.js

RLVuU6AS6qq.js

122 ms

8O2J-mJIMh1.js

8O2J-mJIMh1.js

38 ms

LHNn6iugDK2.js

LHNn6iugDK2.js

121 ms

Q5b8dFH_DSU.js

Q5b8dFH_DSU.js

120 ms

GRa0pv4a7Nk.js

GRa0pv4a7Nk.js

121 ms

p55HfXW__mM.js

p55HfXW__mM.js

187 ms

25lpsvLC9vq.js

25lpsvLC9vq.js

189 ms

0oAcl5WIW_m.js

0oAcl5WIW_m.js

189 ms

settings

settings

240 ms

301970308_643950653967516_7415449188454990974_n.jpg

301970308_643950653967516_7415449188454990974_n.jpg

71 ms

wuH-1da_5h_.js

wuH-1da_5h_.js

15 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

11 ms

GenerateIT

GenerateIT

16 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

30 ms

ROTTEN_KYOTO

ROTTEN_KYOTO

201 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

27 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

58 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

112 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

107 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

108 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

109 ms

_buildManifest.js

_buildManifest.js

111 ms

_ssgManifest.js

_ssgManifest.js

110 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

28 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

27 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

28 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

53 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

59 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

103 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

32 ms

Accessibility Review

rotten-g.com accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

rotten-g.com best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

rotten-g.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Rotten-g.com 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 Rotten-g.com 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

rotten-g.com

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