Access roppay.com. ろっぱ屋 – 管理人が気になったネタを色々紹介。

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

roppay.com

1634 ms

ee2a831a8a3b3b9b199a8fa3a169a59e.css

699 ms

widget.css

351 ms

crayon.min.css

362 ms

jquery.fancybox.css

368 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 25% of them (31 requests) were addressed to the original Roppay.com, 12% (15 requests) were made to Scontent.cdninstagram.com and 7% (8 requests) were made to Ecx.images-amazon.com. The less responsive or slowest element that took the longest time to load (9.5 sec) belongs to the original domain Roppay.com.

Content Size

3.4 MB

After Optimization

2.6 MB

In fact, the total size of Roppay.com main page is 3.4 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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 213.8 kB

Original 236.3 kB
After minification 231.3 kB
After compression 22.5 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 213.8 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 8.9 kB

Original 2.3 MB
After minification 2.3 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. Roppay images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 297.0 kB

Original 502.4 kB
After minification 445.8 kB
After compression 205.4 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 297.0 kB or 59% of the original size.

CSS Optimization

-87%

Potential reduce by 287.2 kB

Original 331.4 kB
After minification 223.0 kB
After compression 44.2 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. Roppay.com needs all CSS files to be minified and compressed as it can save up to 287.2 kB or 87% of the original size.

Requests Now

110

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

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

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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.

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

JA
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roppay.com 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), while the claimed language is Japanese. Our system also found out that Roppay.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

roppay.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

ろっぱ屋 – 管理人が気になったネタを色々紹介。

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

roppay.com

ee2a831a8a3b3b9b199a8fa3a169a59e.css

widget.css

crayon.min.css

jquery.fancybox.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

roppay.com

ee2a831a8a3b3b9b199a8fa3a169a59e.css

widget.css

crayon.min.css

jquery.fancybox.css

wpp.css

jetpack.css

girls-and-panzer_movie4dx_01.jpg

kancolle_winter16_05a.png

embed

51OI0IDhLLL.jpg

embed

embed

adsbygoogle.js

widgets.js

kancolle_winter16_04a.jpg

kancolle_winter16_03a.jpg

venue8pro5855_01a.jpg

kancolle_winter16_02a.jpg

kancolle_winter16_01a.png

q

ns4.js

devicepx-jetpack.js

gprofiles.js

e-201611.js

39a13a2184713036734b36fcc6447293.js

cb=gapi.loaded_0

embed

embed

embed

ca-pub-4747241147888611.js

zrt_lookup.html

show_ads_impl.js

follow_button.1347008535.html

dsL+pqeO67nqoWDyxKSD5NTU3w89PnsCP7e2kY2QERBvOy5ebAvb398Pc3BzYpqZgZmYG7PPzXBxjDTi9Z4VC4SxOIcOmgDabDZaWlmBhYYGUCHlm47dHL9q6ddhPJBrGCXWVBv4DYbnuWKzr2fcAAAAASUVORK5CYII=

profile200200.jpg

ankerlt_02-100x100.jpg

rectv05_01-100x100.jpg

rectv02.jpg

kancolle_summer_e0_01-100x100.jpg

kancolle_summer_e1_01-100x76.jpg

d694a157c1c5fa1e90e5b92b6d7bdb79-100x100.png

kancolle_abu_01-100x100.jpg