Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

interior-nagashima.com

カーテン道の駅201 | 高品質オーダーカーテン・ブラインド等の激安通販

Page Load Speed

9.9 sec in total

First Response

1.7 sec

Resources Loaded

7.5 sec

Page Rendered

660 ms

interior-nagashima.com screenshot

About Website

Welcome to interior-nagashima.com homepage info - get ready to check Interior Nagashima best content for Japan right away, or after learning these important things about interior-nagashima.com

国内一流メーカーのオーダーカーテン、ブラインド、ロールスクリーン、プリーツスクリーン、アコーデオンカーテン、カーペット、クロス等の通販サイト。オーダーメイド品もすぐ発注できる「自動見積」対応品が多数。

Visit interior-nagashima.com

Key Findings

We analyzed Interior-nagashima.com page load time and found that the first response time was 1.7 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

interior-nagashima.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value940 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.281

43/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

interior-nagashima.com

1704 ms

new_curtain.css

2131 ms

new_curtain_est.css

1988 ms

legacy.css

1995 ms

widgets.css

1632 ms

Our browser made a total of 190 requests to load all elements on the main page. We found that 69% of them (131 requests) were addressed to the original Interior-nagashima.com, 11% (20 requests) were made to Static.xx.fbcdn.net and 4% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Interior-nagashima.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 840.2 kB (43%)

Content Size

2.0 MB

After Optimization

1.1 MB

In fact, the total size of Interior-nagashima.com main page is 2.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. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 85.2 kB

  • Original 105.4 kB
  • After minification 104.8 kB
  • After compression 20.2 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 85.2 kB or 81% of the original size.

Image Optimization

-28%

Potential reduce by 372.1 kB

  • Original 1.3 MB
  • After minification 957.9 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. Obviously, Interior Nagashima needs image optimization as it can save up to 372.1 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 288.1 kB

  • Original 409.4 kB
  • After minification 392.3 kB
  • After compression 121.3 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 288.1 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 94.8 kB

  • Original 114.1 kB
  • After minification 89.0 kB
  • After compression 19.3 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. Interior-nagashima.com needs all CSS files to be minified and compressed as it can save up to 94.8 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

186

After Optimization

129

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

Accessibility Review

interior-nagashima.com accessibility score

51

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[role] values are not valid

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

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.

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

interior-nagashima.com best practices score

83

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

SEO Factors

interior-nagashima.com SEO score

82

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 Interior-nagashima.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 Interior-nagashima.com 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 data is detected on the main page of Interior Nagashima. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: