Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

floyd.no

FLOYD

Page Load Speed

3.3 sec in total

First Response

367 ms

Resources Loaded

2.7 sec

Page Rendered

284 ms

floyd.no screenshot

About Website

Click here to check amazing FLOYD content for Norway. Otherwise, check out these important facts you probably never knew about floyd.no

Klær for motebevisste kvinner. Forhandles i 30 Floyd butikker, hos 250 forhandlere i Norge og i nettbutikken - Floyd.no

Visit floyd.no

Key Findings

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

Performance Metrics

floyd.no performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

54/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.74

6/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

floyd.no

367 ms

www.floyd.no

644 ms

prototype.js.pagespeed.jm.ix8Kb1Gh8H.js

362 ms

jquery-1.10.2.min.js.pagespeed.jm.ZzSiN_5Whq.js

388 ms

lib,_jquery,_noconflict.js+lib,_ccard.js+prototype,_validation.js+scriptaculous,_builder.js+scriptaculous,_effects.js.pagespeed.jc.z1YCSxnN2l.js

388 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 41% of them (43 requests) were addressed to the original Floyd.no, 7% (7 requests) were made to Google-analytics.com and 6% (6 requests) were made to Secure.livechatinc.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Scontent.cdninstagram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (54%)

Content Size

3.5 MB

After Optimization

1.6 MB

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

HTML Optimization

-82%

Potential reduce by 125.0 kB

  • Original 152.5 kB
  • After minification 125.2 kB
  • After compression 27.4 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 27.3 kB, which is 18% 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 125.0 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 5.2 kB

  • Original 902.1 kB
  • After minification 896.9 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. FLOYD images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 1.5 MB

  • Original 2.2 MB
  • After minification 2.2 MB
  • After compression 631.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.5 MB or 71% of the original size.

CSS Optimization

-85%

Potential reduce by 237.0 kB

  • Original 278.1 kB
  • After minification 277.0 kB
  • After compression 41.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. Floyd.no needs all CSS files to be minified and compressed as it can save up to 237.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (54%)

Requests Now

90

After Optimization

41

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

Accessibility Review

floyd.no accessibility score

79

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-hidden="true"] elements contain focusable descendents

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

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

floyd.no SEO score

97

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    NB

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floyd.no can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is . Our system also found out that Floyd.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 description is not detected on the main page of FLOYD. 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: