Tools & Wizards About Us
eyemark.co.jp screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

eyemark.co.jp

希望を形にする株式会社アイマーク

Page Load Speed

2.9 sec in total

First Response

505 ms

Resources Loaded

2.3 sec

Page Rendered

55 ms

eyemark.co.jp screenshot

About Website

Welcome to eyemark.co.jp homepage info - get ready to check Eyemark best content right away, or after learning these important things about eyemark.co.jp

株式会社アイマークでは、高伸縮性ツーウェイ素材、吊り編み機による高品質ニット素材、立体裁断、精密加工技術など、ニットの加工に関して無双の技術背景により「ニット製品」の問題解決と、トコトンこだわってモノ作りに取り組んでいます。イベントなど大規模装飾用のスパンデックステントの製作も得意です。

Visit eyemark.co.jp

Key Findings

We analyzed Eyemark.co.jp page load time and found that the first response time was 505 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

eyemark.co.jp performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.161

72/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

eyemark.co.jp

505 ms

eyemark.co.jp

719 ms

www.eyemark.co.jp

869 ms

common.css

190 ms

analytics.js

19 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 80% of them (4 requests) were addressed to the original Eyemark.co.jp, 20% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (869 ms) belongs to the original domain Eyemark.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 kB (5%)

Content Size

23.4 kB

After Optimization

22.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Eyemark.co.jp main page is 23.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 21.0 kB which makes up the majority of the site volume.

HTML Optimization

-55%

Potential reduce by 1.1 kB

  • Original 2.0 kB
  • After minification 1.9 kB
  • After compression 888 B

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 1.1 kB or 55% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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

-17%

Potential reduce by 78 B

  • Original 467 B
  • After minification 467 B
  • After compression 389 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. Eyemark.co.jp needs all CSS files to be minified and compressed as it can save up to 78 B or 17% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyemark. According to our analytics all requests are already optimized.

Network Requests Diagram

eyemark.co.jp

eyemark.co.jp

505 ms

eyemark.co.jp

eyemark.co.jp

719 ms

www.eyemark.co.jp

www.eyemark.co.jp

869 ms

common.css

common.css

190 ms

analytics.js

analytics.js

19 ms

Accessibility Review

eyemark.co.jp accessibility score

95

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.

Best Practices

eyemark.co.jp 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

SEO Factors

eyemark.co.jp 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

Links do not have descriptive text

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyemark.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 Eyemark.co.jp main page’s claimed encoding is shift_jis. 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

eyemark.co.jp

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