Tools & Wizards About Us
rapeco.jp screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

rapeco.jp

おせち取り寄せ｜カニ通販｜正月料理の2017通販ランキングです！

Page Load Speed

7 sec in total

First Response

548 ms

Resources Loaded

5.2 sec

Page Rendered

1.2 sec

rapeco.jp screenshot

About Website

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

お正月といえばおせち料理の食材とカニが必需品ですね。ご当地グルメの格安通販サイトから全国各地の新鮮素材の正月料理を取り寄せましょうね。正月料理の2017通販ランキングです！お取り寄せで人気の高級和牛・焼肉も見逃せません。

Visit rapeco.jp

Key Findings

We analyzed Rapeco.jp page load time and found that the first response time was 548 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

rapeco.jp performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

rapeco.jp

548 ms

www.grandi-falsi.com

537 ms

simplyhyperbarics.com

1007 ms

body.css

344 ms

social.css

344 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rapeco.jp, 57% (47 requests) were made to Simplyhyperbarics.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Simplyhyperbarics.com.

Page Optimization Overview & Recommendations

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

Content Size

5.0 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rapeco.jp main page is 5.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 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 51.2 kB

  • Original 63.2 kB
  • After minification 50.7 kB
  • After compression 12.0 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 12.5 kB, which is 20% 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 51.2 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 98.4 kB

  • Original 4.9 MB
  • After minification 4.8 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. Rapeco images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 517 B

  • Original 108.5 kB
  • After minification 108.5 kB
  • After compression 108.0 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

-74%

Potential reduce by 10.0 kB

  • Original 13.5 kB
  • After minification 11.4 kB
  • After compression 3.5 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. Rapeco.jp needs all CSS files to be minified and compressed as it can save up to 10.0 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (31%)

Requests Now

78

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rapeco.jp

rapeco.jp

548 ms

www.grandi-falsi.com

www.grandi-falsi.com

537 ms

simplyhyperbarics.com

simplyhyperbarics.com

1007 ms

body.css

body.css

344 ms

social.css

social.css

344 ms

widgets.js

widgets.js

13 ms

plusone.js

plusone.js

28 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

95 ms

ga.js

ga.js

95 ms

0.gif

0.gif

337 ms

bgt

bgt

672 ms

0.gif

0.gif

339 ms

0.gif

0.gif

340 ms

0.gif

0.gif

337 ms

0.gif

0.gif

672 ms

0.gif

0.gif

679 ms

0.gif

0.gif

344 ms

0.gif

0.gif

340 ms

bg.png

bg.png

178 ms

header.png

header.png

2052 ms

li.png

li.png

175 ms

rank1.png

rank1.png

335 ms

kanihonpo.png

kanihonpo.png

1664 ms

buy_g.png

buy_g.png

513 ms

rank2.png

rank2.png

345 ms

kanimamire.png

kanimamire.png

1579 ms

rank3.png

rank3.png

498 ms

hokusen_syabu.png

hokusen_syabu.png

1880 ms

osechi_select.png

osechi_select.png

1322 ms

osechi_syokuzai.png

osechi_syokuzai.png

1191 ms

takumi_logo.png

takumi_logo.png

1360 ms

takumi_houraku.png

takumi_houraku.png

1815 ms

kanbai.jpg

kanbai.jpg

1531 ms

hakatahisamatsu_logo.png

hakatahisamatsu_logo.png

1701 ms

hakatahisamatsu_osechi02.png

hakatahisamatsu_osechi02.png

1928 ms

kibun_logo.png

kibun_logo.png

1827 ms

kibun_osechi.png

kibun_osechi.png

2209 ms

kibun_kitty.png

kibun_kitty.png

2145 ms

tonden_logo.png

tonden_logo.png

1993 ms

rank4.png

rank4.png

2049 ms

tonden_osechi.png

tonden_osechi.png

2278 ms

shoujiki_logo.png

shoujiki_logo.png

2159 ms

rank5.png

rank5.png

2217 ms

shoujiki_osechi.png

shoujiki_osechi.png

2389 ms

shoujiki_okuizome.png

shoujiki_okuizome.png

2472 ms

kenkosansai_logo.png

kenkosansai_logo.png

2324 ms

rank6.png

rank6.png

2376 ms

kenkosansai_yasaka.png

kenkosansai_yasaka.png

2730 ms

kenkosansai_poke.png

kenkosansai_poke.png

2454 ms

ikura.jpg

ikura.jpg

2489 ms

li-tuduki.gif

li-tuduki.gif

2546 ms

bgt

bgt

502 ms

0.gif

0.gif

338 ms

bgt

bgt

502 ms

button-only.gif

button-only.gif

58 ms

0.gif

0.gif

331 ms

osusume.jpg

osusume.jpg

2485 ms

osechi03.jpg

osechi03.jpg

2555 ms

why.jpg

why.jpg

2561 ms

bookmark_button.js

bookmark_button.js

35 ms

__utm.gif

__utm.gif

20 ms

button-only.gif

button-only.gif

35 ms

bookmark_button.js

bookmark_button.js

40 ms

like.php

like.php

139 ms

btn.js

btn.js

38 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

56 ms

kanimini.jpg

kanimini.jpg

2486 ms

ranking01.png

ranking01.png

2545 ms

button

button

4 ms

widgetButton.91d9e0cb42c020d8c4b1.css

widgetButton.91d9e0cb42c020d8c4b1.css

19 ms

widgetButton.7edb5a95ac874e928813.js

widgetButton.7edb5a95ac874e928813.js

20 ms

settings

settings

99 ms

TttXWwYVW0v.js

TttXWwYVW0v.js

20 ms

FEppCFCt76d.png

FEppCFCt76d.png

14 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

embeds

embeds

29 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

11 ms

oukany_1.gif

oukany_1.gif

2403 ms

oukany_2.gif

oukany_2.gif

2466 ms

oukany_3.gif

oukany_3.gif

2308 ms

kani_ranking.png

kani_ranking.png

2315 ms

wagyu.png

wagyu.png

2038 ms

left_navi.png

left_navi.png

1584 ms

Accessibility Review

rapeco.jp accessibility score

65

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.

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

rapeco.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Page has valid source maps

SEO Factors

rapeco.jp SEO score

87

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

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rapeco.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rapeco.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

rapeco.jp

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