Access imagic.co.jp. I.MAGIC

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.382

27/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

imagic.co.jp

514 ms

notosansjapanese.css

43 ms

css

69 ms

font-awesome.min.css

16 ms

bootstrap.min.css

27 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 71% of them (29 requests) were addressed to the original Imagic.co.jp, 10% (4 requests) were made to Maxcdn.bootstrapcdn.com and 10% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Imagic.co.jp.

Content Size

2.1 MB

After Optimization

1.8 MB

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

HTML Optimization

-80%

Potential reduce by 10.9 kB

Original 13.6 kB
After minification 10.0 kB
After compression 2.7 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 3.6 kB, which is 26% 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 10.9 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 302 B

Original 1.7 MB
After minification 1.7 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. I MAGIC images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 64.1 kB

Original 157.7 kB
After minification 140.2 kB
After compression 93.6 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 64.1 kB or 41% of the original size.

CSS Optimization

-90%

Potential reduce by 168.3 kB

Original 188.0 kB
After minification 140.5 kB
After compression 19.7 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. Imagic.co.jp needs all CSS files to be minified and compressed as it can save up to 168.3 kB or 90% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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/).

High

Document uses 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 Imagic.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 Imagic.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

imagic.co.jp

Open Graph description is not detected on the main page of I MAGIC. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

I.MAGIC

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)