Tools & Wizards About Us
nijmegen.nl screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

nijmegen.nl

Gemeente Nijmegen

Page Load Speed

4.2 sec in total

First Response

278 ms

Resources Loaded

2.8 sec

Page Rendered

1.1 sec

nijmegen.nl screenshot

About Website

Welcome to nijmegen.nl homepage info - get ready to check Nijmegen best content for Netherlands right away, or after learning these important things about nijmegen.nl

Welkom op de website van de gemeente Nijmegen. Vind hier alle informatie die u als bewoner, ondernemer of bezoeker van Nijmegen wilt weten.

Visit nijmegen.nl

Key Findings

We analyzed Nijmegen.nl page load time and found that the first response time was 278 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

nijmegen.nl performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

nijmegen.nl

278 ms

nijmegen.nl

391 ms

www.nijmegen.nl

730 ms

merged-be9f2cd594ba88086671f49d78859d11.css

184 ms

merged-38f21188133c934527016bcfbb6f0bb7.css

363 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 60% of them (26 requests) were addressed to the original Nijmegen.nl, 26% (11 requests) were made to Componenten.nijmegen.nl and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (921 ms) relates to the external source Componenten.nijmegen.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.9 kB (8%)

Content Size

500.1 kB

After Optimization

462.2 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Nijmegen.nl main page is 500.1 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. 50% of websites need less resources to load. Images take 422.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 37.6 kB

  • Original 47.5 kB
  • After minification 47.1 kB
  • After compression 10.0 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 37.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

CSS Optimization

-1%

Potential reduce by 380 B

  • Original 30.7 kB
  • After minification 30.7 kB
  • After compression 30.3 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. Nijmegen.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (55%)

Requests Now

33

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nijmegen.nl

nijmegen.nl

278 ms

nijmegen.nl

nijmegen.nl

391 ms

www.nijmegen.nl

www.nijmegen.nl

730 ms

merged-be9f2cd594ba88086671f49d78859d11.css

merged-be9f2cd594ba88086671f49d78859d11.css

184 ms

merged-38f21188133c934527016bcfbb6f0bb7.css

merged-38f21188133c934527016bcfbb6f0bb7.css

363 ms

beeldmerklabelrood.svg

beeldmerklabelrood.svg

274 ms

beeldmerk.svg

beeldmerk.svg

275 ms

csm_Foto-homepageNijmegen-nieuw-web_166d32f784.jpg

csm_Foto-homepageNijmegen-nieuw-web_166d32f784.jpg

522 ms

csm_Foto-homepageNijmegen-nieuw-web_24cf4668cd.jpg

csm_Foto-homepageNijmegen-nieuw-web_24cf4668cd.jpg

416 ms

jquery.min.js

jquery.min.js

127 ms

popper.min.js

popper.min.js

137 ms

bootstrap.min.js

bootstrap.min.js

135 ms

mdb.min.js

mdb.min.js

145 ms

nijmegen.js

nijmegen.js

136 ms

Form.min.js

Form.min.js

326 ms

PowermailCondition.min.js

PowermailCondition.min.js

279 ms

pandosearch.js

pandosearch.js

278 ms

colorbox.min.js

colorbox.min.js

430 ms

slick.js

slick.js

574 ms

slickInit.js

slickInit.js

430 ms

pn_easy_vacancies.js

pn_easy_vacancies.js

430 ms

functions.js

functions.js

431 ms

csm_Overzichtsfoto-Winkelsteeg-web-210125_248fdf9692.jpg

csm_Overzichtsfoto-Winkelsteeg-web-210125_248fdf9692.jpg

576 ms

csm_luchtfoto-keizer-karelplein-lowres-website-210225_b0805a3dae.jpg

csm_luchtfoto-keizer-karelplein-lowres-website-210225_b0805a3dae.jpg

688 ms

csm_treinen-still_c19b0c979b.jpg

csm_treinen-still_c19b0c979b.jpg

577 ms

OCYV_logo_wit_wit.svg

OCYV_logo_wit_wit.svg

574 ms

bootstrap.min.css

bootstrap.min.css

9 ms

nijmegen.css

nijmegen.css

16 ms

css

css

71 ms

css

css

57 ms

report.php

report.php

301 ms

facebook.svg

facebook.svg

199 ms

twitter.svg

twitter.svg

303 ms

instagram.svg

instagram.svg

301 ms

linkedin.svg

linkedin.svg

302 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

147 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

151 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

202 ms

materialdesignicons-webfont.c803ff2e.woff

materialdesignicons-webfont.c803ff2e.woff

921 ms

oranda_bt.05235f9a.woff

oranda_bt.05235f9a.woff

527 ms

oranda_bold_bt.8e266873.woff

oranda_bold_bt.8e266873.woff

552 ms

mdb-lightbox-ui.85a282b0.html

mdb-lightbox-ui.85a282b0.html

25 ms

merged-3afd98204ff8d7a06ae1819ac7226434.css

merged-3afd98204ff8d7a06ae1819ac7226434.css

93 ms

Accessibility Review

nijmegen.nl accessibility score

100

Accessibility Issues

Best Practices

nijmegen.nl 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

Missing source maps for large first-party JavaScript

SEO Factors

nijmegen.nl 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 Nijmegen.nl 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 Nijmegen.nl 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

nijmegen.nl

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