Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

tibnor.se

Tibnor.se | Marknadens bredaste utbud av stål och metaller online

Page Load Speed

4.7 sec in total

First Response

399 ms

Resources Loaded

3.4 sec

Page Rendered

954 ms

tibnor.se screenshot

About Website

Visit tibnor.se now to see the best up-to-date Tibnor content for Sweden and also check out these interesting facts you probably never knew about tibnor.se

Tibnor förser industrin i Norden och Baltikum med stål, metaller och tjänster kring bearbetning. Tillsammans gör vi den nordiska industrin ännu starkare.

Visit tibnor.se

Key Findings

We analyzed Tibnor.se page load time and found that the first response time was 399 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

tibnor.se performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value3,330 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value1.467

0/100

15%

TTI (Time to Interactive)

Value24.5 s

0/100

10%

Network Requests Diagram

tibnor.se

399 ms

tibnor.se

334 ms

www.tibnor.se

670 ms

gtm.js

48 ms

fonts.css

357 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 90% of them (108 requests) were addressed to the original Tibnor.se, 4% (5 requests) were made to and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Tibnor.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.0 kB (14%)

Content Size

953.2 kB

After Optimization

818.2 kB

In fact, the total size of Tibnor.se main page is 953.2 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. 65% of websites need less resources to load. Images take 752.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 134.7 kB

  • Original 179.3 kB
  • After minification 151.0 kB
  • After compression 44.6 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 28.3 kB, which is 16% 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 134.7 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 170 B

  • Original 752.8 kB
  • After minification 752.6 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. Tibnor images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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 83 (75%)

Requests Now

111

After Optimization

28

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

Accessibility Review

tibnor.se accessibility score

67

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

High

[lang] attributes do not have a valid value

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

tibnor.se best practices score

75

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

Page has valid source maps

SEO Factors

tibnor.se SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    SV

  • Language Claimed

    SV

  • Encoding

    UTF-8

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