Tools & Wizards About Us
pionaalst.be screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

pionaalst.be

Koninklijke Schaakclub Pion Aalst

Page Load Speed

2.8 sec in total

First Response

481 ms

Resources Loaded

1.9 sec

Page Rendered

435 ms

pionaalst.be screenshot

About Website

Visit pionaalst.be now to see the best up-to-date Pion Aalst content and also check out these interesting facts you probably never knew about pionaalst.be

KS Pion Aalst organiseert clubkampioenschappen, het ajuintornooi, interclubs en jeugdwerking. Er wordt gespeeld elke woensdagavond te Aalst

Visit pionaalst.be

Key Findings

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

pionaalst.be performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

pionaalst.be

481 ms

base.css

171 ms

fotorama.css

911 ms

maps

60 ms

embed

508 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 28% of them (13 requests) were addressed to the original Pionaalst.be, 26% (12 requests) were made to Maps.googleapis.com and 17% (8 requests) were made to Lichess1.org. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Pionaalst.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (70%)

Content Size

1.5 MB

After Optimization

461.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pionaalst.be 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. 50% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 35.7 kB

  • Original 47.3 kB
  • After minification 44.5 kB
  • After compression 11.6 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 35.7 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 515 B

  • Original 23.0 kB
  • After minification 22.5 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. Pion Aalst images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 949.4 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 392.0 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 949.4 kB or 71% of the original size.

CSS Optimization

-73%

Potential reduce by 97.6 kB

  • Original 133.1 kB
  • After minification 132.1 kB
  • After compression 35.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. Pionaalst.be needs all CSS files to be minified and compressed as it can save up to 97.6 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (76%)

Requests Now

42

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pionaalst.be

pionaalst.be

481 ms

base.css

base.css

171 ms

fotorama.css

fotorama.css

911 ms

maps

maps

60 ms

embed

embed

508 ms

embed

embed

509 ms

jquery.js

jquery.js

1120 ms

jquery-ui.js

jquery-ui.js

1234 ms

superfish.js

superfish.js

1094 ms

jquery.slicknav.min.js

jquery.slicknav.min.js

1209 ms

hoverIntent.js

hoverIntent.js

286 ms

jquery.validationEngine-nl.js

jquery.validationEngine-nl.js

476 ms

jquery.validationEngine.js

jquery.validationEngine.js

621 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

770 ms

modernizr.min.js

modernizr.min.js

6 ms

fotorama.js

fotorama.js

1001 ms

embed

embed

378 ms

js

js

93 ms

init_embed.js

init_embed.js

48 ms

frame

frame

118 ms

frame

frame

94 ms

futura_light-normal-webfont.woff

futura_light-normal-webfont.woff

304 ms

common.js

common.js

66 ms

map.js

map.js

87 ms

google4.png

google4.png

44 ms

overlay.js

overlay.js

41 ms

util.js

util.js

157 ms

onion.js

onion.js

114 ms

search_impl.js

search_impl.js

155 ms

merida.css

merida.css

111 ms

common.css

common.css

106 ms

board.css

board.css

112 ms

chessground.min.js

chessground.min.js

105 ms

puzzle.js

puzzle.js

124 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

273 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

143 ms

tv.js

tv.js

142 ms

stats.js

stats.js

118 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

144 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

160 ms

transparent.png

transparent.png

121 ms

kh

kh

312 ms

brown.png

brown.png

98 ms

analytics.js

analytics.js

118 ms

lichess.woff

lichess.woff

176 ms

controls.js

controls.js

172 ms

Accessibility Review

pionaalst.be accessibility score

93

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

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

High

Page has valid source maps

SEO Factors

pionaalst.be SEO score

92

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

pionaalst.be

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