Tools & Wizards About Us
gonewest.be screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    81% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

gonewest.be

Gonewest.be -

Page Load Speed

2.4 sec in total

First Response

289 ms

Resources Loaded

1.8 sec

Page Rendered

243 ms

gonewest.be screenshot

About Website

Click here to check amazing Gonewest content for Belgium. Otherwise, check out these important facts you probably never knew about gonewest.be

Visit gonewest.be

Key Findings

We analyzed Gonewest.be page load time and found that the first response time was 289 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

gonewest.be performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

gonewest.be

289 ms

www.gonewest.be

364 ms

css_FFMDRYZ2nSV6HGDyDVpm9-yNY8H0IkhZ90k-a2N9jFE.css

86 ms

css_mxbvRAV0_YoXwGCXbsQzCkegc1pXHICzfd8PPQD9YE4.css

256 ms

css_i_mOa8cpfGnNXth-wkVqx0Z_SWEosHhtw5OsdQ51tvk.css

170 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 44% of them (18 requests) were addressed to the original Gonewest.be, 15% (6 requests) were made to S7.addthis.com and 7% (3 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (715 ms) belongs to the original domain Gonewest.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 632.7 kB (58%)

Content Size

1.1 MB

After Optimization

463.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gonewest.be main page is 1.1 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. 35% of websites need less resources to load. Javascripts take 557.1 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 68.5 kB

  • Original 93.0 kB
  • After minification 89.6 kB
  • After compression 24.5 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 68.5 kB or 74% of the original size.

Image Optimization

-23%

Potential reduce by 58.0 kB

  • Original 257.0 kB
  • After minification 199.0 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. Obviously, Gonewest needs image optimization as it can save up to 58.0 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 345.3 kB

  • Original 557.1 kB
  • After minification 537.6 kB
  • After compression 211.8 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 345.3 kB or 62% of the original size.

CSS Optimization

-85%

Potential reduce by 160.8 kB

  • Original 189.0 kB
  • After minification 185.8 kB
  • After compression 28.2 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. Gonewest.be needs all CSS files to be minified and compressed as it can save up to 160.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (69%)

Requests Now

35

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gonewest.be

gonewest.be

289 ms

www.gonewest.be

www.gonewest.be

364 ms

css_FFMDRYZ2nSV6HGDyDVpm9-yNY8H0IkhZ90k-a2N9jFE.css

css_FFMDRYZ2nSV6HGDyDVpm9-yNY8H0IkhZ90k-a2N9jFE.css

86 ms

css_mxbvRAV0_YoXwGCXbsQzCkegc1pXHICzfd8PPQD9YE4.css

css_mxbvRAV0_YoXwGCXbsQzCkegc1pXHICzfd8PPQD9YE4.css

256 ms

css_i_mOa8cpfGnNXth-wkVqx0Z_SWEosHhtw5OsdQ51tvk.css

css_i_mOa8cpfGnNXth-wkVqx0Z_SWEosHhtw5OsdQ51tvk.css

170 ms

css_XyELJoL1qsdMTQdFrViNSLevfcrzPM23hhX_NrpUCh0.css

css_XyELJoL1qsdMTQdFrViNSLevfcrzPM23hhX_NrpUCh0.css

171 ms

css

css

24 ms

css_LQwAIC_GxI7LtnabRNKnbQ5AWcNL0WmwlXugLR1ZJxs.css

css_LQwAIC_GxI7LtnabRNKnbQ5AWcNL0WmwlXugLR1ZJxs.css

548 ms

addthis_widget.js

addthis_widget.js

11 ms

jquery.min.js

jquery.min.js

27 ms

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

255 ms

js_fDyuIEGrEBqCopqPxfNZo3fOcNiTp5Sr0AKIgjl2qcw.js

js_fDyuIEGrEBqCopqPxfNZo3fOcNiTp5Sr0AKIgjl2qcw.js

254 ms

js_B6pANnVygoG4zyeowKgq5Ay4PrT1zSbKTj3PQyV__0o.js

js_B6pANnVygoG4zyeowKgq5Ay4PrT1zSbKTj3PQyV__0o.js

336 ms

js_sm_R0t1OCN7zJPpeLFFUOC6QdxU3XidmKIstCvPUt-I.js

js_sm_R0t1OCN7zJPpeLFFUOC6QdxU3XidmKIstCvPUt-I.js

715 ms

analytics.js

analytics.js

67 ms

fbds.js

fbds.js

67 ms

search.png

search.png

101 ms

logo.png

logo.png

102 ms

sprite.png

sprite.png

102 ms

trixie_whitley_hires_0.jpg

trixie_whitley_hires_0.jpg

283 ms

default.jpg

default.jpg

467 ms

widgets.js

widgets.js

219 ms

collect

collect

4 ms

collect

collect

201 ms

35 ms

lgo_prov-west-vlaanderen.png

lgo_prov-west-vlaanderen.png

199 ms

gff3axs.js

gff3axs.js

188 ms

300lo.json

300lo.json

68 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

61 ms

ie67-css.d5089428ac7f05efd372.js

ie67-css.d5089428ac7f05efd372.js

60 ms

counter-ie.033ee35c761079a6df0d.js

counter-ie.033ee35c761079a6df0d.js

58 ms

ga-audiences

ga-audiences

75 ms

icomoon.woff

icomoon.woff

90 ms

tbc04.gif

tbc04.gif

15 ms

shares.json

shares.json

12 ms

nsc01.gif

nsc01.gif

15 ms

1

1

84 ms

p.gif

p.gif

55 ms

p.gif

p.gif

67 ms

cOS7afh0MHhZGMqu_SkZif6XVyLq_H5PFcO7yM5NU36ff4zvMUMmeMI6MK6f5MS.eot

cOS7afh0MHhZGMqu_SkZif6XVyLq_H5PFcO7yM5NU36ff4zvMUMmeMI6MK6f5MS.eot

32 ms

8 ms

Accessibility Review

gonewest.be accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

gonewest.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

gonewest.be SEO score

98

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

gonewest.be

Open Graph description is not detected on the main page of Gonewest. 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: