Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

teller.nl

Web Analytics Made Easy - Statcounter

Page Load Speed

3.4 sec in total

First Response

264 ms

Resources Loaded

3 sec

Page Rendered

129 ms

teller.nl screenshot

About Website

Welcome to teller.nl homepage info - get ready to check Teller best content right away, or after learning these important things about teller.nl

StatCounter is a simple but powerful real-time web analytics service that helps you track, analyse and understand your visitors so you can make good decisions to become more successful online.

Visit teller.nl

Key Findings

We analyzed Teller.nl page load time and found that the first response time was 264 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

teller.nl performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

www.hostingdiscounter.nl

264 ms

www.hostingdiscounter.nl

440 ms

jquery-ui.min.css

140 ms

jqModal.css

230 ms

main.css

453 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Teller.nl, 8% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (975 ms) relates to the external source Hostingdiscounter.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 356.3 kB (62%)

Content Size

577.7 kB

After Optimization

221.4 kB

In fact, the total size of Teller.nl main page is 577.7 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. 20% of websites need less resources to load. Javascripts take 384.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 16.8 kB

  • Original 20.1 kB
  • After minification 13.2 kB
  • After compression 3.3 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 7.0 kB, which is 35% 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 16.8 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 9.4 kB

  • Original 98.9 kB
  • After minification 89.5 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. Teller images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 268.8 kB

  • Original 384.7 kB
  • After minification 356.8 kB
  • After compression 115.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 268.8 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 61.2 kB

  • Original 73.9 kB
  • After minification 59.8 kB
  • After compression 12.7 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. Teller.nl needs all CSS files to be minified and compressed as it can save up to 61.2 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

23

After Optimization

14

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

Accessibility Review

teller.nl accessibility score

82

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.

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 [lang] attribute

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

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

teller.nl best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

teller.nl SEO score

92

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teller.nl can be misinterpreted by Google and other search engines. Our service has detected that English 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 Teller.nl 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 Teller. 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: