Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

septis.co.jp

SELECT STORE SEPTIS / TOPページ

Page Load Speed

13.7 sec in total

First Response

1.4 sec

Resources Loaded

10.7 sec

Page Rendered

1.6 sec

septis.co.jp screenshot

About Website

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

東京世田谷三軒茶屋のインポートブランドのセレクトショップセプティズです。メンズファッションあこがれの商品、定番のアイテム、雑誌掲載商品を取り扱っております

Visit septis.co.jp

Key Findings

We analyzed Septis.co.jp page load time and found that the first response time was 1.4 sec and then it took 12.3 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

septis.co.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

septis.co.jp

1387 ms

common.css

356 ms

jquery.slider.css

355 ms

jquery.simplyscroll-1.0.4.css

542 ms

jquery.min.js

7 ms

Our browser made a total of 176 requests to load all elements on the main page. We found that 80% of them (140 requests) were addressed to the original Septis.co.jp, 7% (12 requests) were made to Pbs.twimg.com and 3% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Septis.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (14%)

Content Size

8.7 MB

After Optimization

7.5 MB

In fact, the total size of Septis.co.jp main page is 8.7 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. Images take 8.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 60.2 kB

  • Original 71.1 kB
  • After minification 58.9 kB
  • After compression 11.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.2 kB, which is 17% 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 60.2 kB or 85% of the original size.

Image Optimization

-12%

Potential reduce by 1.0 MB

  • Original 8.4 MB
  • After minification 7.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. Obviously, SEPTIS needs image optimization as it can save up to 1.0 MB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-50%

Potential reduce by 40.8 kB

  • Original 81.2 kB
  • After minification 78.3 kB
  • After compression 40.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 40.8 kB or 50% of the original size.

CSS Optimization

-82%

Potential reduce by 71.6 kB

  • Original 87.0 kB
  • After minification 76.0 kB
  • After compression 15.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. Septis.co.jp needs all CSS files to be minified and compressed as it can save up to 71.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (17%)

Requests Now

174

After Optimization

145

The browser has sent 174 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SEPTIS. 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 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

septis.co.jp accessibility score

72

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

septis.co.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

septis.co.jp SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

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 Septis.co.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 Septis.co.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 SEPTIS. 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: