Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

bt.no

Bergens Tidende

Page Load Speed

47.1 sec in total

First Response

288 ms

Resources Loaded

44.5 sec

Page Rendered

2.3 sec

bt.no screenshot

About Website

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

Vestlandets største regionavis med alltid oppdaterte nyheter innenfor innenriks, utenriks, sport og kultur.

Visit bt.no

Key Findings

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

Performance Metrics

bt.no performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value1,760 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

bt.no

288 ms

www.bt.no

631 ms

css

26 ms

www.bt.no

715 ms

www.bt.no

362 ms

Our browser made a total of 246 requests to load all elements on the main page. We found that 10% of them (25 requests) were addressed to the original Bt.no, 32% (79 requests) were made to Bt.mnocdn.no and 6% (14 requests) were made to Ocacache.medianorge.no. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Bt.mnocdn.no.

Page Optimization Overview & Recommendations

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

Content Size

9.9 MB

After Optimization

8.4 MB

In fact, the total size of Bt.no main page is 9.9 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. 80% 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 8.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 217.7 kB

  • Original 267.5 kB
  • After minification 263.7 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 217.7 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 58.3 kB

  • Original 8.0 MB
  • After minification 7.9 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. Bt images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 754.3 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 417.0 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 754.3 kB or 64% of the original size.

CSS Optimization

-87%

Potential reduce by 386.6 kB

  • Original 442.7 kB
  • After minification 361.1 kB
  • After compression 56.2 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. Bt.no needs all CSS files to be minified and compressed as it can save up to 386.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 86 (37%)

Requests Now

233

After Optimization

147

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

Accessibility Review

bt.no accessibility score

82

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] values are not valid

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

Heading elements are not in a sequentially-descending order

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

    NO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bt.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Bt.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 Bt. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: