Tools & Wizards About Us
discusprothese.be screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

discusprothese.be

Page Load Speed

5.9 sec in total

First Response

314 ms

Resources Loaded

5.3 sec

Page Rendered

280 ms

discusprothese.be screenshot

About Website

Click here to check amazing Discusprothese content. Otherwise, check out these important facts you probably never knew about discusprothese.be

Visit discusprothese.be

Key Findings

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

Performance Metrics

discusprothese.be performance score

0

Network Requests Diagram

discusprothese.be

314 ms

neurochirurgie-limburg.com

374 ms

www.neurochirurgie-limburg.com

804 ms

style.css

449 ms

fancybox-1.3.4.min.css

2014 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Discusprothese.be, 58% (25 requests) were made to Neurochirurgie4u.be and 33% (14 requests) were made to Neurochirurgie-limburg.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Neurochirurgie4u.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.7 kB (4%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Discusprothese.be main page is 1.7 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. 30% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-48%

Potential reduce by 396 B

  • Original 826 B
  • After minification 826 B
  • After compression 430 B

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 396 B or 48% of the original size.

Image Optimization

-1%

Potential reduce by 17.7 kB

  • Original 1.6 MB
  • After minification 1.6 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. Discusprothese images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 18.5 kB

  • Original 45.3 kB
  • After minification 43.8 kB
  • After compression 26.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 18.5 kB or 41% of the original size.

CSS Optimization

-82%

Potential reduce by 34.1 kB

  • Original 41.6 kB
  • After minification 33.9 kB
  • After compression 7.5 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. Discusprothese.be needs all CSS files to be minified and compressed as it can save up to 34.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (27%)

Requests Now

41

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

discusprothese.be

discusprothese.be

314 ms

neurochirurgie-limburg.com

neurochirurgie-limburg.com

374 ms

www.neurochirurgie-limburg.com

www.neurochirurgie-limburg.com

804 ms

style.css

style.css

449 ms

fancybox-1.3.4.min.css

fancybox-1.3.4.min.css

2014 ms

files.css

files.css

2015 ms

jquery.min.js

jquery.min.js

7 ms

modernizr-1.6.min.js

modernizr-1.6.min.js

1081 ms

fancybox-1.3.4.min.js

fancybox-1.3.4.min.js

1006 ms

main.js

main.js

2002 ms

ga.js

ga.js

66 ms

bg.png

bg.png

87 ms

overlay.png

overlay.png

406 ms

home.jpg

home.jpg

89 ms

menubg.jpg

menubg.jpg

86 ms

dropdownbg.jpg

dropdownbg.jpg

87 ms

logo-neurochirurgie.png

logo-neurochirurgie.png

163 ms

searchbg.png

searchbg.png

243 ms

4way.jpg

4way.jpg

244 ms

neurosurgery.jpg

neurosurgery.jpg

165 ms

syndromes.jpg

syndromes.jpg

164 ms

brochures.jpg

brochures.jpg

244 ms

surgicaltechniques.jpg

surgicaltechniques.jpg

247 ms

sidebarbg.jpg

sidebarbg.jpg

246 ms

li.png

li.png

324 ms

footerbg.jpg

footerbg.jpg

325 ms

homefooter.jpg

homefooter.jpg

326 ms

menufooterbg.jpg

menufooterbg.jpg

330 ms

logoinset.jpg

logoinset.jpg

329 ms

credits.png

credits.png

405 ms

1.jpg

1.jpg

566 ms

2.jpg

2.jpg

1562 ms

3.jpg

3.jpg

809 ms

4.jpg

4.jpg

1604 ms

5.jpg

5.jpg

1654 ms

6.jpg

6.jpg

1645 ms

7.jpg

7.jpg

876 ms

8.jpg

8.jpg

1131 ms

9.jpg

9.jpg

1279 ms

10.jpg

10.jpg

1292 ms

11.jpg

11.jpg

1441 ms

12.jpg

12.jpg

1777 ms

__utm.gif

__utm.gif

13 ms

Accessibility Review

discusprothese.be accessibility score

33

Accessibility Issues

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

Document doesn't have a <title> element

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

Best Practices

discusprothese.be best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

discusprothese.be SEO score

50

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

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discusprothese.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Discusprothese.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

discusprothese.be

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