Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

mobileweb.t-mobile.nl

T-Mobile is nu Odido | T-Mobile

Page Load Speed

3.1 sec in total

First Response

275 ms

Resources Loaded

2.6 sec

Page Rendered

242 ms

mobileweb.t-mobile.nl screenshot

About Website

Welcome to mobileweb.t-mobile.nl homepage info - get ready to check Mobile Web T best content for Netherlands right away, or after learning these important things about mobileweb.t-mobile.nl

T-Mobile is nu Odido. Bestel je mobiele abonnement, met of zonder telefoon. Ontdek daarnaast internet, TV en Vast Bellen van T-Mobile. Stel je eigen pakket samen!

Visit mobileweb.t-mobile.nl

Key Findings

We analyzed Mobileweb.t-mobile.nl page load time and found that the first response time was 275 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

mobileweb.t-mobile.nl performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.25

49/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

mobileweb.t-mobile.nl

275 ms

m.t-mobile.nl

273 ms

home

89 ms

www.t-mobile.nl

648 ms

Main

360 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Mobileweb.t-mobile.nl, 70% (14 requests) were made to T-mobile.nl and 10% (2 requests) were made to M.t-mobile.nl. The less responsive or slowest element that took the longest time to load (955 ms) relates to the external source T-mobile.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.9 kB (9%)

Content Size

427.4 kB

After Optimization

389.5 kB

In fact, the total size of Mobileweb.t-mobile.nl main page is 427.4 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. 15% of websites need less resources to load. Images take 363.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 33.7 kB

  • Original 41.6 kB
  • After minification 30.9 kB
  • After compression 7.9 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 10.7 kB, which is 26% 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 33.7 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 4.1 kB

  • Original 363.5 kB
  • After minification 359.4 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. Mobile Web T images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 75 B

  • Original 22.3 kB
  • After minification 22.3 kB
  • After compression 22.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 5 (36%)

Requests Now

14

After Optimization

9

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Web T. 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 as a result speed up the page load time.

Accessibility Review

mobileweb.t-mobile.nl accessibility score

91

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.

Best Practices

mobileweb.t-mobile.nl best practices score

83

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

SEO Factors

mobileweb.t-mobile.nl SEO score

97

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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