Tools & Wizards About Us
mobilevikings.be screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

mobilevikings.be

Mobile Vikings | Sharpest price for internet, mobile and at home

Page Load Speed

7.4 sec in total

First Response

112 ms

Resources Loaded

4.2 sec

Page Rendered

3 sec

mobilevikings.be screenshot

About Website

Visit mobilevikings.be now to see the best up-to-date Mobile Vikings content for Belgium and also check out these interesting facts you probably never knew about mobilevikings.be

Surf super fast on your mobile with ridiculous amounts of data, or choose unlimited internet at home at top speed. Always at the sharpest price.

Visit mobilevikings.be

Key Findings

We analyzed Mobilevikings.be page load time and found that the first response time was 112 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

mobilevikings.be performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value18.7 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value4,040 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.822

4/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

mobilevikings.be

112 ms

799 ms

style.min.css

296 ms

style.css

285 ms

elementor-icons.min.css

305 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 71% of them (49 requests) were addressed to the original Mobilevikings.be, 7% (5 requests) were made to Ire-s3-prod-mv-cms.s3.eu-west-1.amazonaws.com and 3% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Mobilevikings.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 437.7 kB (45%)

Content Size

970.5 kB

After Optimization

532.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobilevikings.be main page is 970.5 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. 70% of websites need less resources to load. HTML takes 471.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 411.2 kB

  • Original 471.4 kB
  • After minification 451.6 kB
  • After compression 60.2 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 411.2 kB or 87% of the original size.

Image Optimization

-9%

Potential reduce by 23.5 kB

  • Original 253.9 kB
  • After minification 230.3 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 Vikings images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 963 B

  • Original 81.5 kB
  • After minification 81.5 kB
  • After compression 80.5 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.

CSS Optimization

-1%

Potential reduce by 2.0 kB

  • Original 163.6 kB
  • After minification 163.6 kB
  • After compression 161.6 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. Mobilevikings.be has all CSS files already compressed.

Requests Breakdown

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

Requests Now

55

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobilevikings.be

mobilevikings.be

112 ms

799 ms

style.min.css

style.min.css

296 ms

style.css

style.css

285 ms

elementor-icons.min.css

elementor-icons.min.css

305 ms

frontend-legacy.min.css

frontend-legacy.min.css

301 ms

frontend.min.css

frontend.min.css

373 ms

frontend.min.css

frontend.min.css

426 ms

all.min.css

all.min.css

559 ms

v4-shims.min.css

v4-shims.min.css

510 ms

css

css

65 ms

fontawesome.min.css

fontawesome.min.css

370 ms

solid.min.css

solid.min.css

302 ms

v4-shims.min.js

v4-shims.min.js

581 ms

vue.min.js

vue.min.js

67 ms

vue-app.umd.min.js

vue-app.umd.min.js

1061 ms

vue-app.css

vue-app.css

856 ms

bundle.tracing.es6.min.js

bundle.tracing.es6.min.js

53 ms

jquery.min.js

jquery.min.js

51 ms

IntersectionObserver.js

IntersectionObserver.js

72 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

477 ms

webpack.runtime.min.js

webpack.runtime.min.js

550 ms

jquery.min.js

jquery.min.js

628 ms

jquery-migrate.min.js

jquery-migrate.min.js

612 ms

frontend-modules.min.js

frontend-modules.min.js

619 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

640 ms

wp-polyfill.min.js

wp-polyfill.min.js

685 ms

hooks.min.js

hooks.min.js

895 ms

i18n.min.js

i18n.min.js

699 ms

frontend.min.js

frontend.min.js

718 ms

waypoints.min.js

waypoints.min.js

760 ms

core.min.js

core.min.js

771 ms

frontend.min.js

frontend.min.js

798 ms

elements-handlers.min.js

elements-handlers.min.js

1360 ms

scripts.min.js

scripts.min.js

1361 ms

gtm.js

gtm.js

215 ms

factuur.png

factuur.png

1042 ms

diamant.png

diamant.png

1121 ms

hart.png

hart.png

1121 ms

helm.png

helm.png

1119 ms

logo-white.svg

logo-white.svg

312 ms

icon-cookies.svg

icon-cookies.svg

226 ms

close.svg

close.svg

490 ms

icon-check.svg

icon-check.svg

224 ms

470 ms

mralex-bold.woff

mralex-bold.woff

208 ms

mralex-bold.woff2

mralex-bold.woff2

353 ms

forosans-bold.woff

forosans-bold.woff

932 ms

forosans-extrabold.woff

forosans-extrabold.woff

351 ms

forosans-regular.woff

forosans-regular.woff

932 ms

icon-chevron_down-grey.svg

icon-chevron_down-grey.svg

917 ms

M4_0190.jpg

M4_0190.jpg

1201 ms

fa-solid-900.woff

fa-solid-900.woff

912 ms

fa-regular-400.woff

fa-regular-400.woff

939 ms

optimize.js

optimize.js

802 ms

m42epxv4.js

m42epxv4.js

687 ms

5oouj4xux2

5oouj4xux2

770 ms

forosans-extrabold.ttf

forosans-extrabold.ttf

577 ms

mralex-bold.ttf

mralex-bold.ttf

583 ms

landing

landing

232 ms

diagonal-red-faded-lines.png

diagonal-red-faded-lines.png

260 ms

icon-bell-redDots.svg

icon-bell-redDots.svg

225 ms

m42epxv4.json

m42epxv4.json

107 ms

forosans-extrabold.svg

forosans-extrabold.svg

109 ms

clarity.js

clarity.js

77 ms

runtime.d457904.js

runtime.d457904.js

178 ms

js

js

38 ms

non-critical.css

non-critical.css

148 ms

c.gif

c.gif

41 ms

Accessibility Review

mobilevikings.be accessibility score

71

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

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

mobilevikings.be 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

Missing source maps for large first-party JavaScript

SEO Factors

mobilevikings.be SEO score

84

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

High

Tap targets are not sized appropriately

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 Mobilevikings.be 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 Mobilevikings.be 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

mobilevikings.be

Open Graph data is detected on the main page of Mobile Vikings. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: