Tools & Wizards About Us
simulise.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

simulise.com

Het digitaal portfolio dat vaardigheden zichtbaar maakt - Simulise

Page Load Speed

2.2 sec in total

First Response

37 ms

Resources Loaded

1.1 sec

Page Rendered

1.1 sec

simulise.com screenshot

About Website

Visit simulise.com now to see the best up-to-date Simulise content for Netherlands and also check out these interesting facts you probably never knew about simulise.com

Zoek je het beste digitaal portfolio voor je school? Doe mee met onze wekelijkse webinar en zie wat Simulise jouw leerlingen kan bieden! Simulise biedt een levenslang portfolio en inzicht in de ontwik...

Visit simulise.com

Key Findings

We analyzed Simulise.com page load time and found that the first response time was 37 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

simulise.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

55/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

simulise.com

37 ms

simulise.com

139 ms

www.simulise.com

205 ms

style.min.css

63 ms

styles.css

86 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 98% of them (40 requests) were addressed to the original Simulise.com, 2% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (485 ms) belongs to the original domain Simulise.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 197.2 kB (13%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Simulise.com main page is 1.5 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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 109.3 kB

  • Original 145.4 kB
  • After minification 145.3 kB
  • After compression 36.1 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 109.3 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-73%

Potential reduce by 87.9 kB

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

CSS Optimization

-0%

Potential reduce by 49 B

  • Original 69.0 kB
  • After minification 69.0 kB
  • After compression 68.9 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. Simulise.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

33

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

simulise.com

simulise.com

37 ms

simulise.com

simulise.com

139 ms

www.simulise.com

www.simulise.com

205 ms

style.min.css

style.min.css

63 ms

styles.css

styles.css

86 ms

style.min.css

style.min.css

78 ms

style.min.css

style.min.css

84 ms

simulise.main.css

simulise.main.css

95 ms

slick.css

slick.css

55 ms

rocket-loader.min.js

rocket-loader.min.js

58 ms

nl.svg

nl.svg

67 ms

en.svg

en.svg

71 ms

Ontwerp-zonder-titel-56.png

Ontwerp-zonder-titel-56.png

123 ms

PO.svg

PO.svg

113 ms

VO.svg

VO.svg

118 ms

MBO.svg

MBO.svg

114 ms

HO.svg

HO.svg

120 ms

Simulise-demo-3-1.png

Simulise-demo-3-1.png

122 ms

uc.js

uc.js

133 ms

AvenirLTStd-Roman.woff

AvenirLTStd-Roman.woff

142 ms

Lexend-Medium.woff

Lexend-Medium.woff

129 ms

Lexend-Regular.woff

Lexend-Regular.woff

192 ms

Lexend-SemiBold.woff

Lexend-SemiBold.woff

485 ms

Lexend-Bold.woff

Lexend-Bold.woff

142 ms

lazyload.min.js

lazyload.min.js

26 ms

Ontwerp-zonder-titel-57.png

Ontwerp-zonder-titel-57.png

26 ms

Voorbeeld-portfolio-Alexa.png

Voorbeeld-portfolio-Alexa.png

48 ms

Group-525.png

Group-525.png

63 ms

Group-526.png

Group-526.png

91 ms

Group-590.png

Group-590.png

184 ms

Group-592.png

Group-592.png

203 ms

medal-thin.png

medal-thin.png

145 ms

file-circle-plus-thin.png

file-circle-plus-thin.png

146 ms

Group-593-1.png

Group-593-1.png

144 ms

Berichten-omslag-800-x-534-px.png

Berichten-omslag-800-x-534-px.png

146 ms

Josetta-Hak-Conrector-800-x-534-px-5.jpg

Josetta-Hak-Conrector-800-x-534-px-5.jpg

146 ms

Josetta-Hak-Conrector-800-x-534-px-1.png

Josetta-Hak-Conrector-800-x-534-px-1.png

146 ms

social-linkedin.png

social-linkedin.png

147 ms

social-facebook.png

social-facebook.png

147 ms

social-instagram.png

social-instagram.png

148 ms

social-youtube.png

social-youtube.png

157 ms

Accessibility Review

simulise.com accessibility score

83

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.

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

Links do not have a discernible name

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

simulise.com best practices score

92

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

SEO Factors

simulise.com SEO score

100

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

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 Simulise.com 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 Simulise.com 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

simulise.com

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