Tools & Wizards About Us
archiefalkmaar.nl screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

archiefalkmaar.nl

Home - Regionaal Archief Alkmaar

Page Load Speed

3.2 sec in total

First Response

262 ms

Resources Loaded

2.5 sec

Page Rendered

393 ms

archiefalkmaar.nl screenshot

About Website

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

Regionaal Archief te Alkmaar, intergemeentelijk samenwerkingsverband in Noord-Kennemerland, westelijk West-Friesland en de Kop van Noord-Holland. Bewaart archieven van overheden en particulieren in di...

Visit archiefalkmaar.nl

Key Findings

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

Performance Metrics

archiefalkmaar.nl performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

archiefalkmaar.nl

262 ms

www.regionaalarchiefalkmaar.nl

332 ms

www.regionaalarchiefalkmaar.nl

483 ms

modal.css

84 ms

template.css

247 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Archiefalkmaar.nl, 56% (31 requests) were made to Regionaalarchiefalkmaar.nl and 24% (13 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (776 ms) relates to the external source Regionaalarchiefalkmaar.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 432.1 kB (23%)

Content Size

1.9 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Archiefalkmaar.nl main page is 1.9 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 22.6 kB

  • Original 28.7 kB
  • After minification 22.9 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 5.7 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.6 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 39.1 kB

  • Original 1.4 MB
  • After minification 1.3 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. Archief Alkmaar images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 272.1 kB

  • Original 397.3 kB
  • After minification 381.9 kB
  • After compression 125.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 272.1 kB or 68% of the original size.

CSS Optimization

-89%

Potential reduce by 98.3 kB

  • Original 110.8 kB
  • After minification 72.9 kB
  • After compression 12.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. Archiefalkmaar.nl needs all CSS files to be minified and compressed as it can save up to 98.3 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (31%)

Requests Now

51

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

archiefalkmaar.nl

archiefalkmaar.nl

262 ms

www.regionaalarchiefalkmaar.nl

www.regionaalarchiefalkmaar.nl

332 ms

www.regionaalarchiefalkmaar.nl

www.regionaalarchiefalkmaar.nl

483 ms

modal.css

modal.css

84 ms

template.css

template.css

247 ms

slimbox.css

slimbox.css

258 ms

mootools-core.js

mootools-core.js

356 ms

core.js

core.js

270 ms

caption.js

caption.js

274 ms

modal.js

modal.js

279 ms

mootools-more.js

mootools-more.js

493 ms

raa.js

raa.js

335 ms

nl_slimbox.js

nl_slimbox.js

377 ms

slideshow.js

slideshow.js

376 ms

ga.js

ga.js

69 ms

body_bg.jpg

body_bg.jpg

178 ms

logo.png

logo.png

283 ms

backgrounds.png

backgrounds.png

480 ms

arrow_down.png

arrow_down.png

104 ms

mediaspace_DHopdekaart.jpg

mediaspace_DHopdekaart.jpg

574 ms

mediaspace_homepage_cursussen.jpg

mediaspace_homepage_cursussen.jpg

658 ms

mediaspace_homepage_blog.jpg

mediaspace_homepage_blog.jpg

597 ms

open_data_mediaspace_homepage.jpg

open_data_mediaspace_homepage.jpg

675 ms

workarea_bg.jpg

workarea_bg.jpg

369 ms

archiefnieuw3.jpg

archiefnieuw3.jpg

481 ms

genealogie3.jpg

genealogie3.jpg

565 ms

raa%20007003806%20-%201996%20-%20gemeente%20bergen.jpg

raa%20007003806%20-%201996%20-%20gemeente%20bergen.jpg

572 ms

catalogus.jpg

catalogus.jpg

652 ms

kranten.jpg

kranten.jpg

664 ms

tijdschrijften3.jpg

tijdschrijften3.jpg

660 ms

opdekaart.jpg

opdekaart.jpg

776 ms

widgets.js

widgets.js

153 ms

OfficinaSansStd-Book.woff

OfficinaSansStd-Book.woff

767 ms

__utm.gif

__utm.gif

22 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

30 ms

syndication

syndication

79 ms

346987784139055105

346987784139055105

94 ms

proxy.jpg

proxy.jpg

124 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

37 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

121 ms

TJRu6wCk_normal.jpg

TJRu6wCk_normal.jpg

89 ms

Mv4fgDci_normal.jpg

Mv4fgDci_normal.jpg

87 ms

Logo-final_normal.png

Logo-final_normal.png

140 ms

gnZ0_Hsr_normal.png

gnZ0_Hsr_normal.png

86 ms

l7Le7VLB_normal.jpg

l7Le7VLB_normal.jpg

143 ms

CdrNKqMXEAAWszp.jpg:small

CdrNKqMXEAAWszp.jpg:small

87 ms

CdqUTh5VIAA13E0.jpg:small

CdqUTh5VIAA13E0.jpg:small

87 ms

CdlKs1PWoAANLAm.jpg:small

CdlKs1PWoAANLAm.jpg:small

88 ms

CdlC1VpXEAAgjSW.jpg:small

CdlC1VpXEAAgjSW.jpg:small

98 ms

CdLZIZOUAAAK8Dp.jpg:small

CdLZIZOUAAAK8Dp.jpg:small

135 ms

CdG6YL-UMAAPOb1.jpg:small

CdG6YL-UMAAPOb1.jpg:small

130 ms

CdBwzkjUYAA0xKr.jpg:small

CdBwzkjUYAA0xKr.jpg:small

158 ms

CdBHk56W8AEFpor.jpg:small

CdBHk56W8AEFpor.jpg:small

139 ms

jot

jot

24 ms

print.css

print.css

83 ms

Accessibility Review

archiefalkmaar.nl accessibility score

84

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

archiefalkmaar.nl best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

archiefalkmaar.nl SEO score

91

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

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

archiefalkmaar.nl

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