Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

creema.jp

Creema(クリーマ) |国内最大のハンドメイドマーケットプレイス

Page Load Speed

7.3 sec in total

First Response

403 ms

Resources Loaded

6.3 sec

Page Rendered

576 ms

creema.jp screenshot

About Website

Welcome to creema.jp homepage info - get ready to check Creema best content for Japan right away, or after learning these important things about creema.jp

ハンドメイド・クリエイター作品を購入・販売できる Creema。普通のお店では売っていないファッション・アクセサリー・インテリアなどが1400万点以上。人とかぶらない、クリエイターのこだわりが詰まった1点ものを選んでみませんか。

Visit creema.jp

Key Findings

We analyzed Creema.jp page load time and found that the first response time was 403 ms and then it took 6.9 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

creema.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value600 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value1.569

0/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

creema.jp

403 ms

www.creema.jp

936 ms

fullsite-base.20160223191456.min.css

448 ms

top.css

301 ms

top.css

306 ms

Our browser made a total of 284 requests to load all elements on the main page. We found that 25% of them (72 requests) were addressed to the original Creema.jp, 54% (152 requests) were made to D12ciics2fd1e.cloudfront.net and 5% (14 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source D12ciics2fd1e.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 592.1 kB (14%)

Content Size

4.2 MB

After Optimization

3.6 MB

In fact, the total size of Creema.jp main page is 4.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 150.8 kB

  • Original 181.0 kB
  • After minification 144.1 kB
  • After compression 30.3 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 37.0 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 150.8 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 19.8 kB

  • Original 3.4 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. Creema images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 310.4 kB

  • Original 494.6 kB
  • After minification 490.6 kB
  • After compression 184.2 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 310.4 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 111.0 kB

  • Original 134.0 kB
  • After minification 122.8 kB
  • After compression 23.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. Creema.jp needs all CSS files to be minified and compressed as it can save up to 111.0 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

279

After Optimization

207

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

Accessibility Review

creema.jp accessibility score

56

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-hidden="true"] elements contain focusable descendents

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.

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

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

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

creema.jp best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

creema.jp SEO score

77

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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