Tools & Wizards About Us
lynx.be screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

lynx.be

Online beleggen via LYNX | Dé online broker die beleggen serieus neemt

Page Load Speed

5.9 sec in total

First Response

93 ms

Resources Loaded

3.9 sec

Page Rendered

1.9 sec

lynx.be screenshot

About Website

Welcome to lynx.be homepage info - get ready to check LYNX best content for Belgium right away, or after learning these important things about lynx.be

Online broker LYNX => Uw volgende stap in Online beleggen - Handel als een pro op 100+ beurzen in aandelen, opties, futures, forex + ETF's!

Visit lynx.be

Key Findings

We analyzed Lynx.be page load time and found that the first response time was 93 ms and then it took 5.8 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

lynx.be performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value3,510 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

lynx.be

93 ms

lynx.be

154 ms

www.lynx.be

340 ms

uc.js

48 ms

91988347.js

406 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 97% of them (85 requests) were addressed to the original Lynx.be, 1% (1 request) were made to Consent.cookiebot.com and 1% (1 request) were made to Cdn.ablyft.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Lynx.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 395.1 kB (40%)

Content Size

990.6 kB

After Optimization

595.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lynx.be main page is 990.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 367.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 305.9 kB

  • Original 367.8 kB
  • After minification 366.1 kB
  • After compression 61.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. 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 305.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 177.9 kB
  • After minification 177.9 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. LYNX images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 88.9 kB

  • Original 338.8 kB
  • After minification 338.8 kB
  • After compression 249.9 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 88.9 kB or 26% of the original size.

CSS Optimization

-0%

Potential reduce by 348 B

  • Original 106.1 kB
  • After minification 106.1 kB
  • After compression 105.7 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. Lynx.be has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 74 (95%)

Requests Now

78

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lynx.be

lynx.be

93 ms

lynx.be

lynx.be

154 ms

www.lynx.be

www.lynx.be

340 ms

uc.js

uc.js

48 ms

91988347.js

91988347.js

406 ms

style.min.css

style.min.css

156 ms

market_tiles_css.082a6f1e51a059371665.css

market_tiles_css.082a6f1e51a059371665.css

14 ms

6959.69733c8e.css

6959.69733c8e.css

10 ms

main.0c63ba0b.css

main.0c63ba0b.css

14 ms

amazonpolly-public.css

amazonpolly-public.css

9 ms

stu-frontend.css

stu-frontend.css

9 ms

stylesheet.css

stylesheet.css

8 ms

forms.d02a3cb2.css

forms.d02a3cb2.css

11 ms

results-page.css

results-page.css

11 ms

perfect-scrollbar-0.4.6.min.css

perfect-scrollbar-0.4.6.min.css

13 ms

style.css

style.css

9 ms

slider.778ff1e5.css

slider.778ff1e5.css

26 ms

accordion.c0808fbf.css

accordion.c0808fbf.css

24 ms

fontAwesome.3f5b4e2b.css

fontAwesome.3f5b4e2b.css

13 ms

marketing.13640231.css

marketing.13640231.css

16 ms

spacing-utilities.f637fe7a.css

spacing-utilities.f637fe7a.css

17 ms

jquery.min.js

jquery.min.js

222 ms

jquery-migrate.min.js

jquery-migrate.min.js

157 ms

advertisement.js

advertisement.js

29 ms

754.js

754.js

28 ms

440.js

440.js

31 ms

script.js

script.js

31 ms

perfect-scrollbar-0.4.6.with-mousewheel.min.js

perfect-scrollbar-0.4.6.with-mousewheel.min.js

36 ms

performanceTile.5b1b5fe4.css

performanceTile.5b1b5fe4.css

43 ms

search-universal.1a2763f2.css

search-universal.1a2763f2.css

50 ms

languageselect.3e0f67ac.css

languageselect.3e0f67ac.css

46 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

51 ms

slider.js

slider.js

12 ms

accordion.js

accordion.js

13 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

76 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

146 ms

wp-polyfill.min.js

wp-polyfill.min.js

220 ms

dom-ready.min.js

dom-ready.min.js

169 ms

hooks.min.js

hooks.min.js

213 ms

i18n.min.js

i18n.min.js

231 ms

a11y.min.js

a11y.min.js

446 ms

jquery.json.min.js

jquery.json.min.js

158 ms

runtime.f148c8c7.js

runtime.f148c8c7.js

166 ms

2702.2acd58cc.js

2702.2acd58cc.js

172 ms

9154.377ef2a8.js

9154.377ef2a8.js

169 ms

4462.1935e2e6.js

4462.1935e2e6.js

172 ms

38.9ee0645e.js

38.9ee0645e.js

177 ms

1194.ee5ca698.js

1194.ee5ca698.js

175 ms

7912.78c90ae9.js

7912.78c90ae9.js

180 ms

6523.2ae2fe59.js

6523.2ae2fe59.js

182 ms

4227.5b7ccbbb.js

4227.5b7ccbbb.js

183 ms

9640.329972a3.js

9640.329972a3.js

183 ms

main.3d3912c4.js

main.3d3912c4.js

185 ms

lazysizes.min.js

lazysizes.min.js

199 ms

322.js

322.js

188 ms

182.js

182.js

202 ms

992.js

992.js

201 ms

422.js

422.js

204 ms

dismiss.js

dismiss.js

203 ms

57.js

57.js

208 ms

gravityForms.89e79807.js

gravityForms.89e79807.js

206 ms

7167.4552c8ec.js

7167.4552c8ec.js

208 ms

accordion.ac445401.js

accordion.ac445401.js

209 ms

marketing.0656485e.js

marketing.0656485e.js

214 ms

disclaimer.4c78654b.js

disclaimer.4c78654b.js

208 ms

cookies_up.9c3c2774.js

cookies_up.9c3c2774.js

208 ms

248.js

248.js

210 ms

299.js

299.js

197 ms

871.js

871.js

148 ms

8177.7d4ddae9.js

8177.7d4ddae9.js

133 ms

514.659c83df.js

514.659c83df.js

79 ms

7875.e4c02f17.js

7875.e4c02f17.js

71 ms

2867.93a8f2e1.js

2867.93a8f2e1.js

66 ms

307.f04bfca4.js

307.f04bfca4.js

59 ms

performanceTile.9429dbff.js

performanceTile.9429dbff.js

59 ms

lazyload.min.js

lazyload.min.js

58 ms

gtm.js

gtm.js

271 ms

gradient-5-1.png

gradient-5-1.png

164 ms

default.min.css

default.min.css

74 ms

GT-Pressura-Regular.3b88e6f1.woff

GT-Pressura-Regular.3b88e6f1.woff

134 ms

fa-light-300.2006c9ff.ttf

fa-light-300.2006c9ff.ttf

137 ms

fa-regular-400.ba0c0a75.ttf

fa-regular-400.ba0c0a75.ttf

280 ms

fa-solid-900.6fa0a823.ttf

fa-solid-900.6fa0a823.ttf

136 ms

press-bold.23466532.woff

press-bold.23466532.woff

278 ms

falynx.76e5d99a.ttf

falynx.76e5d99a.ttf

45 ms

2123 ms

fa-brands-400.0601cf57.ttf

fa-brands-400.0601cf57.ttf

30 ms

tablepress-responsive.min.css

tablepress-responsive.min.css

4 ms

Accessibility Review

lynx.be accessibility score

74

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

lynx.be best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

lynx.be SEO score

93

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

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

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 Lynx.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 Lynx.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

lynx.be

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