Tools & Wizards About Us

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

frient.dk

frient - sensors, alarms, smart plugs - home care and security

Page Load Speed

22.7 sec in total

First Response

389 ms

Resources Loaded

22 sec

Page Rendered

323 ms

About Website

Visit frient.dk now to see the best up-to-date Frient content and also check out these interesting facts you probably never knew about frient.dk

Meet your new smart home frients. Frients are Zigbee-based smart home devices that help you automate and protect your home and look after your loved ones.

Visit frient.dk

Key Findings

We analyzed Frient.dk page load time and found that the first response time was 389 ms and then it took 22.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

frient.dk performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.146

77/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

frient.dk

389 ms

frient.dk

478 ms

gtm.js

95 ms

7072ffd84b69bca911cc6daa2.js

77 ms

master.min.css

121 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 67% of them (14 requests) were addressed to the original Frient.dk, 10% (2 requests) were made to Chimpstatic.com and 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Cdn.polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 281.4 kB (6%)

Content Size

4.8 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frient.dk main page is 4.8 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. 25% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 86.0 kB

  • Original 97.7 kB
  • After minification 97.7 kB
  • After compression 11.7 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 86.0 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 78.5 kB

  • Original 4.5 MB
  • After minification 4.4 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. Frient images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 110.3 kB

  • Original 212.6 kB
  • After minification 211.5 kB
  • After compression 102.3 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 110.3 kB or 52% of the original size.

CSS Optimization

-31%

Potential reduce by 6.6 kB

  • Original 21.6 kB
  • After minification 21.6 kB
  • After compression 15.0 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. Frient.dk needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (56%)

Requests Now

16

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

frient.dk accessibility score

76

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-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

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

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

frient.dk 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

frient.dk SEO score

93

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frient.dk 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 Frient.dk 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 Frient. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: