Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

sancity.jp

日本最大級!安心安全で安いカラコンやコスメも揃う!カラコン・コスメ通販【サンシティ】公式サイト

Page Load Speed

36.7 sec in total

First Response

588 ms

Resources Loaded

33 sec

Page Rendered

3.1 sec

sancity.jp screenshot

About Website

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

日本最大級の品ぞろえ!安心安全な国内承認レンズで安いカラコンや話題を集める韓国コスメなどの通販と言えばサンシティ!送料無料商品も多数あり。最短当日発送可能!度ありも度なしも幅広く展開中!後払いやAmazonPayなど支払方法も豊富なのが魅力的。安心に通販を楽しむならサンシティにお任せ!

Visit sancity.jp

Key Findings

We analyzed Sancity.jp page load time and found that the first response time was 588 ms and then it took 36.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

sancity.jp performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.624

10/100

15%

TTI (Time to Interactive)

Value57.8 s

0/100

10%

Network Requests Diagram

sancity.jp

588 ms

www.sancity.jp

2204 ms

common.css

2664 ms

head.js

961 ms

jquery-1.7.1.min.js

2948 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 97% of them (145 requests) were addressed to the original Sancity.jp, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Tenso.com. The less responsive or slowest element that took the longest time to load (13.7 sec) belongs to the original domain Sancity.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 867.7 kB (9%)

Content Size

9.3 MB

After Optimization

8.4 MB

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

HTML Optimization

-83%

Potential reduce by 45.8 kB

  • Original 55.2 kB
  • After minification 44.3 kB
  • After compression 9.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 10.9 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 45.8 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 657.5 kB

  • Original 9.0 MB
  • After minification 8.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. Sancity images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 108.8 kB

  • Original 171.1 kB
  • After minification 147.9 kB
  • After compression 62.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 108.8 kB or 64% of the original size.

CSS Optimization

-87%

Potential reduce by 55.6 kB

  • Original 64.2 kB
  • After minification 45.3 kB
  • After compression 8.6 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. Sancity.jp needs all CSS files to be minified and compressed as it can save up to 55.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (7%)

Requests Now

147

After Optimization

137

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

Accessibility Review

sancity.jp accessibility score

70

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

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

Form elements do not have associated labels

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

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

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

sancity.jp SEO score

83

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

    UTF-8

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