Tools & Wizards About Us
inkart.be screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

inkart.be

INKART IN- & OUTDOOR KARTING - A12 Antwerpen-Brussel - Puurs |

Page Load Speed

5.2 sec in total

First Response

337 ms

Resources Loaded

4.7 sec

Page Rendered

188 ms

inkart.be screenshot

About Website

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

Inkart is sinds 1994 de toonaangevende karting in België gelegen in de regio Antwerpen langs de A12 ter hoogte van Willebroek, Boom en Puurs. Je kan karten op het indoorkarting circuit en bij droog we...

Visit inkart.be

Key Findings

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

Performance Metrics

inkart.be performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.083

93/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

inkart.be

337 ms

www.inkart.be

896 ms

modules,_node,_node.css,qn+modules,_system,_defaults.css,qn+modules,_system,_system.css,qn+modules,_system,_system-menus.css,qn+modules,_user,_user.css,qn+sites,_all,_modules,_cck,_theme,_content-module.css,qn+sites,_all,_modules,_filefield,_filefield.css,qn+sites,_all,_modules,_lightbox2,_css,_lightbox.css,qn+sites,_all,_modules,_og,_theme,_og.css,qn+sites,_all,_modules,_views_slideshow,_contrib,_views_slideshow_singleframe,_views_slideshow.css,qn+sites,_all,_modules,_cck,_modules,_fieldgroup,_fieldgroup.css,qn+sites,_all,_modules,_views,_css,_views.css,qn+sites,_all,_themes,_inkart,_css,_960_24.css,qn+sites,_all,_themes,_inkart,_css,_style.css,qn+sites,_all,_themes,_inkart,_li-scroller.css,qn.pagespeed.cc.5zPbqTcOCS.css

337 ms

js_9f5c4df8164edbf7012acce1643ec19c.js.pagespeed.ce.8RoFaIqWOG.js

620 ms

bgheader01.jpg

2830 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 93% of them (25 requests) were addressed to the original Inkart.be, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Inkart.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 189.0 kB (20%)

Content Size

937.3 kB

After Optimization

748.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inkart.be main page is 937.3 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. 15% of websites need less resources to load. Images take 702.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 14.9 kB

  • Original 20.7 kB
  • After minification 20.6 kB
  • After compression 5.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 14.9 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 20.2 kB

  • Original 702.5 kB
  • After minification 682.2 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. INKART images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 113.9 kB

  • Original 167.1 kB
  • After minification 135.1 kB
  • After compression 53.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 113.9 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 39.9 kB

  • Original 47.0 kB
  • After minification 30.9 kB
  • After compression 7.0 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. Inkart.be needs all CSS files to be minified and compressed as it can save up to 39.9 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INKART. According to our analytics all requests are already optimized.

Network Requests Diagram

inkart.be

inkart.be

337 ms

www.inkart.be

www.inkart.be

896 ms

modules,_node,_node.css,qn+modules,_system,_defaults.css,qn+modules,_system,_system.css,qn+modules,_system,_system-menus.css,qn+modules,_user,_user.css,qn+sites,_all,_modules,_cck,_theme,_content-module.css,qn+sites,_all,_modules,_filefield,_filefield.css,qn+sites,_all,_modules,_lightbox2,_css,_lightbox.css,qn+sites,_all,_modules,_og,_theme,_og.css,qn+sites,_all,_modules,_views_slideshow,_contrib,_views_slideshow_singleframe,_views_slideshow.css,qn+sites,_all,_modules,_cck,_modules,_fieldgroup,_fieldgroup.css,qn+sites,_all,_modules,_views,_css,_views.css,qn+sites,_all,_themes,_inkart,_css,_960_24.css,qn+sites,_all,_themes,_inkart,_css,_style.css,qn+sites,_all,_themes,_inkart,_li-scroller.css,qn.pagespeed.cc.5zPbqTcOCS.css

modules,_node,_node.css,qn+modules,_system,_defaults.css,qn+modules,_system,_system.css,qn+modules,_system,_system-menus.css,qn+modules,_user,_user.css,qn+sites,_all,_modules,_cck,_theme,_content-module.css,qn+sites,_all,_modules,_filefield,_filefield.css,qn+sites,_all,_modules,_lightbox2,_css,_lightbox.css,qn+sites,_all,_modules,_og,_theme,_og.css,qn+sites,_all,_modules,_views_slideshow,_contrib,_views_slideshow_singleframe,_views_slideshow.css,qn+sites,_all,_modules,_cck,_modules,_fieldgroup,_fieldgroup.css,qn+sites,_all,_modules,_views,_css,_views.css,qn+sites,_all,_themes,_inkart,_css,_960_24.css,qn+sites,_all,_themes,_inkart,_css,_style.css,qn+sites,_all,_themes,_inkart,_li-scroller.css,qn.pagespeed.cc.5zPbqTcOCS.css

337 ms

js_9f5c4df8164edbf7012acce1643ec19c.js.pagespeed.ce.8RoFaIqWOG.js

js_9f5c4df8164edbf7012acce1643ec19c.js.pagespeed.ce.8RoFaIqWOG.js

620 ms

bgheader01.jpg

bgheader01.jpg

2830 ms

carbon01.png

carbon01.png

1269 ms

phone.gif.pagespeed.ce.tATZRVnSC_.gif

phone.gif.pagespeed.ce.tATZRVnSC_.gif

119 ms

xlogo_site.jpg.pagespeed.ic.J0SgFFgNrY.jpg

xlogo_site.jpg.pagespeed.ic.J0SgFFgNrY.jpg

299 ms

menuzone.jpg

menuzone.jpg

319 ms

background01.jpg

background01.jpg

2372 ms

buttonbusiness.png.pagespeed.ce.S-fOk2Ym_y.png

buttonbusiness.png.pagespeed.ce.S-fOk2Ym_y.png

683 ms

buttonparticulier.png.pagespeed.ce.DrP4HrgKzI.png

buttonparticulier.png.pagespeed.ce.DrP4HrgKzI.png

1621 ms

buttonbistro.png.pagespeed.ce.ZS1oxjuR4s.png

buttonbistro.png.pagespeed.ce.ZS1oxjuR4s.png

1521 ms

headerblockfront.png

headerblockfront.png

797 ms

contentblock_front.png

contentblock_front.png

910 ms

100x33xInkart-Buttons,P20Mailing-02.jpg.pagespeed.ic.U6jztIryGc.jpg

100x33xInkart-Buttons,P20Mailing-02.jpg.pagespeed.ic.U6jztIryGc.jpg

1022 ms

100x33xInkart-Buttons,P20Mailing-04.jpg.pagespeed.ic.tYWwxZXluq.jpg

100x33xInkart-Buttons,P20Mailing-04.jpg.pagespeed.ic.tYWwxZXluq.jpg

1136 ms

60x29xfacebook-logo.jpg.pagespeed.ic.PdhYgPZVPd.jpg

60x29xfacebook-logo.jpg.pagespeed.ic.PdhYgPZVPd.jpg

1249 ms

xchrono.png.pagespeed.ic.-UoSx6rpw0.png

xchrono.png.pagespeed.ic.-UoSx6rpw0.png

1363 ms

Action-button-website-2.png.pagespeed.ce.tXl5Gk6o2M.png

Action-button-website-2.png.pagespeed.ce.tXl5Gk6o2M.png

1610 ms

movies.png.pagespeed.ce.5JQQtmwsPK.png

movies.png.pagespeed.ce.5JQQtmwsPK.png

2257 ms

races.png.pagespeed.ce.n4XtICYgVm.png

races.png.pagespeed.ce.n4XtICYgVm.png

2619 ms

footerblock_front.png

footerblock_front.png

1714 ms

footer.jpg

footer.jpg

2295 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

11 ms

bannerbg.png

bannerbg.png

1769 ms

Accessibility Review

inkart.be accessibility score

96

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 input fields do not have accessible names

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.

Best Practices

inkart.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inkart.be SEO score

97

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

inkart.be

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