Tools & Wizards About Us

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

schenker.no

Global logistikk | Forsyningskjedestyring | DB SCHENKER

Page Load Speed

5 sec in total

First Response

193 ms

Resources Loaded

3.2 sec

Page Rendered

1.7 sec

About Website

Visit schenker.no now to see the best up-to-date SCHENKER content and also check out these interesting facts you probably never knew about schenker.no

Ser du etter et logistikk- og forsyningskjedeteam som forstår virksomheten din? Fra øyeblikkelig bestilling til avanserte løsninger spesifikke for din bransje, vårt globale nettverk og lokale eksperti...

Visit schenker.no

Key Findings

We analyzed Schenker.no page load time and found that the first response time was 193 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

schenker.no performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value1,700 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

www.dbschenker.no

193 ms

www.dbschenker.no

375 ms

478 ms

global-2-810662-57.js

184 ms

global-2-810666-67.css

363 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Schenker.no, 15% (5 requests) were made to Gstatic.com and 12% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Chatbotcdn.dbschenker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (58%)

Content Size

2.7 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Schenker.no main page is 2.7 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. 45% of websites need less resources to load. Javascripts take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 189.7 kB

  • Original 223.7 kB
  • After minification 223.6 kB
  • After compression 34.0 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 189.7 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.2 kB
  • After minification 2.2 kB

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. SCHENKER images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 1.4 MB

  • Original 2.4 MB
  • After minification 2.4 MB
  • After compression 1.1 MB

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 1.4 MB or 56% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 24.6 kB
  • After minification 24.6 kB
  • After compression 24.6 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. Schenker.no has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (81%)

Requests Now

27

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

schenker.no accessibility score

77

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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

Best Practices

schenker.no 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

schenker.no SEO score

92

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

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Schenker.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Schenker.no 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 data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: