Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

romapri.com

かわいいお姫様系インテリア家具・雑貨の通販|ロマプリ・ロマンティックプリンセス

Page Load Speed

15.4 sec in total

First Response

571 ms

Resources Loaded

14.5 sec

Page Rendered

378 ms

romapri.com screenshot

About Website

Click here to check amazing Romapri content for Japan. Otherwise, check out these important facts you probably never knew about romapri.com

かわいいお姫様系インテリア家具・雑貨のロマンティックプリンセス(ロマプリ)。アンティーク調・クラシカルなデザイン、猫脚家具などのアイテムを多数取り扱っています。ロマンティックプリンセス(ロマプリ)はネット通販のスクロールR&Dが運営しています。

Visit romapri.com

Key Findings

We analyzed Romapri.com page load time and found that the first response time was 571 ms and then it took 14.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

romapri.com performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value37.2 s

0/100

25%

SI (Speed Index)

Value50.0 s

0/100

10%

TBT (Total Blocking Time)

Value39,420 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.816

4/100

15%

TTI (Time to Interactive)

Value131.3 s

0/100

10%

Network Requests Diagram

romapri.com

571 ms

top.aspx

1656 ms

default.css

508 ms

PartsRecentlyViewedItems.css

350 ms

alert.css

367 ms

Our browser made a total of 147 requests to load all elements on the main page. We found that 88% of them (130 requests) were addressed to the original Romapri.com, 2% (3 requests) were made to Track.mk.impact-ad.jp and 2% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Romapri.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (57%)

Content Size

3.0 MB

After Optimization

1.3 MB

In fact, the total size of Romapri.com main page is 3.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. 45% of websites need less resources to load. CSS take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 70.6 kB

  • Original 86.0 kB
  • After minification 77.9 kB
  • After compression 15.4 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 70.6 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 24.7 kB

  • Original 922.8 kB
  • After minification 898.2 kB

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. Romapri images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 616.4 kB

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

CSS Optimization

-89%

Potential reduce by 1.0 MB

  • Original 1.1 MB
  • After minification 898.6 kB
  • After compression 129.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. Romapri.com needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (34%)

Requests Now

142

After Optimization

94

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

Accessibility Review

romapri.com accessibility score

86

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

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

High

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

Best Practices

romapri.com 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

romapri.com SEO score

80

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

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

    SHIFT_JIS

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

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