Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

dakine.ch

Dakine Europe | Backpacks, Luggage, Surf, Snow, & Bike Gear Since 1979

Page Load Speed

10.7 sec in total

First Response

289 ms

Resources Loaded

9.8 sec

Page Rendered

575 ms

dakine.ch screenshot

About Website

Visit dakine.ch now to see the best up-to-date Dakine content for Switzerland and also check out these interesting facts you probably never knew about dakine.ch

Dakine builds backpacks, bags, outerwear, gloves and accessories for surf, skate, snowboard, ski, mountain bike, windsurf, and kite.

Visit dakine.ch

Key Findings

We analyzed Dakine.ch page load time and found that the first response time was 289 ms and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

dakine.ch performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value26.1 s

0/100

25%

SI (Speed Index)

Value26.8 s

0/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.628

9/100

15%

TTI (Time to Interactive)

Value29.7 s

0/100

10%

Network Requests Diagram

dakine.ch

289 ms

dakine.ch

389 ms

www.dakine-europe.com

658 ms

dakine-europe.com

4207 ms

calendar.min.css

107 ms

Our browser made a total of 211 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Dakine.ch, 90% (190 requests) were made to Dakine-europe.com and 4% (8 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Dakine-europe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 438.2 kB (11%)

Content Size

4.0 MB

After Optimization

3.5 MB

In fact, the total size of Dakine.ch main page is 4.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 261.6 kB

  • Original 311.4 kB
  • After minification 300.6 kB
  • After compression 49.8 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 261.6 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 169.1 kB

  • Original 3.3 MB
  • After minification 3.2 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. Dakine images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 224 B

  • Original 107.4 kB
  • After minification 107.4 kB
  • After compression 107.2 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

-3%

Potential reduce by 7.2 kB

  • Original 219.5 kB
  • After minification 219.4 kB
  • After compression 212.3 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. Dakine.ch has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 153 (78%)

Requests Now

195

After Optimization

42

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

Accessibility Review

dakine.ch accessibility score

66

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

[role]s do not have all required [aria-*] attributes

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

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dakine.ch best practices score

58

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

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dakine.ch SEO score

85

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 uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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