Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

tandberg.no

Telepresence - Next Generation of Video Conferencing | Cisco Systems

Page Load Speed

2.1 sec in total

First Response

160 ms

Resources Loaded

1.8 sec

Page Rendered

157 ms

tandberg.no screenshot

About Website

Click here to check amazing Tandberg content. Otherwise, check out these important facts you probably never knew about tandberg.no

TelePresence helps individuals and businesses around the world be more productive by enabling face-to-face collaboration.

Visit tandberg.no

Key Findings

We analyzed Tandberg.no page load time and found that the first response time was 160 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

tandberg.no performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

tandberg.no

160 ms

tandberg.html

81 ms

masterbrand.min.js

170 ms

popup.mb.min.js

620 ms

masterbrand.min.css

621 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tandberg.no, 90% (38 requests) were made to Cisco.com and 5% (2 requests) were made to Dpm.demdex.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Cisco.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 350.0 kB (56%)

Content Size

625.9 kB

After Optimization

276.0 kB

In fact, the total size of Tandberg.no main page is 625.9 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. 35% of websites need less resources to load. CSS take 327.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 3.7 kB

  • Original 5.3 kB
  • After minification 4.4 kB
  • After compression 1.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 915 B, which is 17% 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 3.7 kB or 70% of the original size.

Image Optimization

-2%

Potential reduce by 781 B

  • Original 40.4 kB
  • After minification 39.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. Tandberg images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 87.8 kB

  • Original 253.0 kB
  • After minification 252.6 kB
  • After compression 165.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 87.8 kB or 35% of the original size.

CSS Optimization

-79%

Potential reduce by 257.7 kB

  • Original 327.3 kB
  • After minification 322.9 kB
  • After compression 69.5 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. Tandberg.no needs all CSS files to be minified and compressed as it can save up to 257.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (85%)

Requests Now

39

After Optimization

6

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

Accessibility Review

tandberg.no accessibility score

79

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.

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

tandberg.no best practices score

50

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

SEO Factors

tandberg.no SEO score

69

Search Engine Optimization Advices

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 Tandberg.no 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 Tandberg.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 Tandberg. 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: