Tools & Wizards About Us

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

no.farnell.com

Farnell Norge - distributør av elektronikkomponenter

Page Load Speed

15.1 sec in total

First Response

6.2 sec

Resources Loaded

8.5 sec

Page Rendered

408 ms

About Website

Welcome to no.farnell.com homepage info - get ready to check No Farnell best content for United Kingdom right away, or after learning these important things about no.farnell.com

Elektronikkomponentdistributøren Farnell Norge selger halvledere, passive komponenter og mye mer. Lave priser, rask levering!

Visit no.farnell.com

Key Findings

We analyzed No.farnell.com page load time and found that the first response time was 6.2 sec and then it took 8.9 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

no.farnell.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

no.farnell.com

6220 ms

global.css

50 ms

mkglobal.css

27 ms

revoHeader_europe.css

20 ms

mk-styles-global-overrides.css

25 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 89% of them (114 requests) were addressed to the original No.farnell.com, 7% (9 requests) were made to Server.iad.liveperson.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain No.farnell.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (71%)

Content Size

2.0 MB

After Optimization

561.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of No.farnell.com main page is 2.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. 65% of websites need less resources to load. CSS take 721.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 168.9 kB

  • Original 206.1 kB
  • After minification 179.2 kB
  • After compression 37.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 26.9 kB, which is 13% 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 168.9 kB or 82% of the original size.

Image Optimization

-47%

Potential reduce by 177.8 kB

  • Original 378.7 kB
  • After minification 200.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. Obviously, No Farnell needs image optimization as it can save up to 177.8 kB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 442.4 kB

  • Original 649.2 kB
  • After minification 580.6 kB
  • After compression 206.8 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 442.4 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 604.1 kB

  • Original 721.0 kB
  • After minification 674.7 kB
  • After compression 116.9 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. No.farnell.com needs all CSS files to be minified and compressed as it can save up to 604.1 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

126

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

no.farnell.com accessibility score

83

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements 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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

no.farnell.com best practices score

75

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

no.farnell.com SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    NO

  • Encoding

    UTF-8

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