Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

rumors.jp

ファッション通販 rumors(ルモアズ)

Page Load Speed

10.2 sec in total

First Response

775 ms

Resources Loaded

8.9 sec

Page Rendered

533 ms

rumors.jp screenshot

About Website

Visit rumors.jp now to see the best up-to-date Rumors content for India and also check out these interesting facts you probably never knew about rumors.jp

ファッション通販サイトrumors(ルモアズ)はメンズ・レディースを問わず、アパレル、コスメ、雑貨などの情報満載!上品で洗練された大人の為のファッションオンラインストアです。

Visit rumors.jp

Key Findings

We analyzed Rumors.jp page load time and found that the first response time was 775 ms 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.

Performance Metrics

rumors.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value22.8 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.123

84/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

Network Requests Diagram

rumors.jp

775 ms

rumors_bst.css

384 ms

reset.css

373 ms

cssfonts.css

372 ms

style.css

378 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 41% of them (43 requests) were addressed to the original Rumors.jp, 46% (48 requests) were made to Fsimg.rumors.jp and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Fsimg.rumors.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 481.3 kB (12%)

Content Size

4.1 MB

After Optimization

3.6 MB

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

HTML Optimization

-85%

Potential reduce by 82.3 kB

  • Original 97.4 kB
  • After minification 75.4 kB
  • After compression 15.1 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 22.0 kB, which is 23% 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 82.3 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 214.2 kB

  • Original 3.7 MB
  • After minification 3.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. Rumors images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 143.3 kB

  • Original 248.0 kB
  • After minification 245.3 kB
  • After compression 104.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 143.3 kB or 58% of the original size.

CSS Optimization

-84%

Potential reduce by 41.6 kB

  • Original 49.6 kB
  • After minification 32.2 kB
  • After compression 8.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. Rumors.jp needs all CSS files to be minified and compressed as it can save up to 41.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (14%)

Requests Now

102

After Optimization

88

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

Accessibility Review

rumors.jp accessibility score

88

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

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

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

rumors.jp 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

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

rumors.jp SEO score

82

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

Image elements do not have [alt] attributes

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 Rumors.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 Rumors.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

Open Graph description is not detected on the main page of Rumors. 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: