Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

dbschenker-seino.jp

グローバルロジスティクスソリューション&サプライチェーンマネジメント | DB Schenker

Page Load Speed

2.8 sec in total

First Response

289 ms

Resources Loaded

2.4 sec

Page Rendered

142 ms

dbschenker-seino.jp screenshot

About Website

Visit dbschenker-seino.jp now to see the best up-to-date DB Schenker Seino content and also check out these interesting facts you probably never knew about dbschenker-seino.jp

皆さまのビジネスを理解しているロジスティクス&サプライチェーンの担当チームをお探しですか?インスタント予約から高度な業種別ソリューションまで、世界規模のネットワークとローカルな専門性で先を行きます。皆さまの業務をサポートします。

Visit dbschenker-seino.jp

Key Findings

We analyzed Dbschenker-seino.jp page load time and found that the first response time was 289 ms and then it took 2.5 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

dbschenker-seino.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value730 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.122

84/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

www.dbschenker-seino.jp

289 ms

479 ms

layout2010-common-dbtype,f456af5c30082d58f9529c9c300744b5ae95f2fd.css

479 ms

site-common-dbtype,1f95d2b57175db3519aa89df53b095a5b58c07df.css

238 ms

dbsearch.autocomplete.css.css

223 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 94% of them (33 requests) were addressed to the original Dbschenker-seino.jp, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (887 ms) belongs to the original domain Dbschenker-seino.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.8 kB (71%)

Content Size

114.1 kB

After Optimization

33.3 kB

In fact, the total size of Dbschenker-seino.jp main page is 114.1 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. 25% of websites need less resources to load. HTML takes 96.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 80.8 kB

  • Original 96.9 kB
  • After minification 94.8 kB
  • After compression 16.1 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 80.8 kB or 83% of the original size.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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.

Requests Breakdown

Number of requests can be reduced by 14 (48%)

Requests Now

29

After Optimization

15

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DB Schenker Seino. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

dbschenker-seino.jp accessibility score

83

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 input fields do not have accessible names

High

ARIA IDs are not unique

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

Links do not have a discernible name

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

dbschenker-seino.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dbschenker-seino.jp SEO score

89

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dbschenker-seino.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Dbschenker-seino.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 DB Schenker Seino. 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: