Tools & Wizards About Us

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

taketomo.co.jp

医薬品,ＰＴＰ包装,食品包材,包装材料,ＩＣタグアンテナ製造,ＰＴＰ用アルミ箔,ラミネートフイルムの株式会社タケトモ

Page Load Speed

8.9 sec in total

First Response

637 ms

Resources Loaded

8.1 sec

Page Rendered

128 ms

About Website

Visit taketomo.co.jp now to see the best up-to-date Taketomo content and also check out these interesting facts you probably never knew about taketomo.co.jp

医薬品,ＰＴＰ包装,食品包材,包装材料,ＩＣタグアンテナ製造,ＰＴＰ用アルミ箔,ラミネートフイルム,両面図柄合わせ,バーコード印刷, (株)タケトモ。東京都新宿区高田馬場1－33－5電話03-3209-7231。ＰＶＣ,ＣＰＰシート

Visit taketomo.co.jp

Key Findings

We analyzed Taketomo.co.jp page load time and found that the first response time was 637 ms and then it took 8.3 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

taketomo.co.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.336

33/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

taketomo.co.jp

637 ms

2079 ms

common.css

244 ms

style.css

453 ms

style-en.css

581 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 96% of them (48 requests) were addressed to the original Taketomo.co.jp, 2% (1 request) were made to Ajax.googleapis.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Taketomo.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

3.4 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 30.6 kB

  • Original 37.7 kB
  • After minification 33.7 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 4.1 kB, which is 11% 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 30.6 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 12.5 kB

  • Original 3.0 MB
  • After minification 2.9 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. Taketomo images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 143.9 kB

  • Original 240.7 kB
  • After minification 236.1 kB
  • After compression 96.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 143.9 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 128.0 kB

  • Original 151.1 kB
  • After minification 140.6 kB
  • After compression 23.1 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. Taketomo.co.jp needs all CSS files to be minified and compressed as it can save up to 128.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (42%)

Requests Now

48

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

taketomo.co.jp accessibility score

81

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.

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

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

taketomo.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

taketomo.co.jp SEO score

74

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Taketomo.co.jp can be misinterpreted by Google and other search engines. Our service has detected that English 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 Taketomo.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 Taketomo. 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: