Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

box-i.net

手作り石鹸素材・軽石粉末の専門店

Page Load Speed

3.1 sec in total

First Response

562 ms

Resources Loaded

2.5 sec

Page Rendered

99 ms

box-i.net screenshot

About Website

Click here to check amazing Box I content for Japan. Otherwise, check out these important facts you probably never knew about box-i.net

粉末軽石のマイルドなスクラブ効果により、ひじ、ひざ、かかとの角質を洗いながら落とす軽石石鹸づくりの副材料としてご利用いただけます。

Visit box-i.net

Key Findings

We analyzed Box-i.net page load time and found that the first response time was 562 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

box-i.net performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value2,630 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

box-i.net

562 ms

main1.css

174 ms

show_ads.js

66 ms

adsbygoogle.js

112 ms

001.gif

344 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 89% of them (16 requests) were addressed to the original Box-i.net, 11% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Box-i.net.

Page Optimization Overview & Recommendations

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

Content Size

91.7 kB

After Optimization

83.6 kB

In fact, the total size of Box-i.net main page is 91.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 80.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 8.0 kB

  • Original 10.3 kB
  • After minification 7.5 kB
  • After compression 2.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 2.8 kB, which is 27% 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 8.0 kB or 77% of the original size.

JavaScript Optimization

-0%

Potential reduce by 30 B

  • Original 80.8 kB
  • After minification 80.8 kB
  • After compression 80.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 111 B

  • Original 582 B
  • After minification 582 B
  • After compression 471 B

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. Box-i.net needs all CSS files to be minified and compressed as it can save up to 111 B or 19% of the original size.

Requests Breakdown

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

Requests Now

17

After Optimization

10

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

Accessibility Review

box-i.net accessibility score

84

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

box-i.net best practices score

75

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

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

box-i.net SEO score

67

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Box-i.net 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 Box-i.net main page’s claimed encoding is euc-jp. 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 Box I. 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: