Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

readingpen.nl

Lexima.nl - Lexima, voor beter lezen en leren

Page Load Speed

699 ms in total

First Response

288 ms

Resources Loaded

295 ms

Page Rendered

116 ms

readingpen.nl screenshot

About Website

Visit readingpen.nl now to see the best up-to-date Readingp En content and also check out these interesting facts you probably never knew about readingpen.nl

Lexima speelt een grote rol in de verspreiding van kennis over de aanpak van leesproblemen, het bestrijden van laaggeletterdheid en het omgaan met dyslexie.

Visit readingpen.nl

Key Findings

We analyzed Readingpen.nl page load time and found that the first response time was 288 ms and then it took 411 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

readingpen.nl performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

readingpen.nl

288 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Readingpen.nl and no external sources were called. The less responsive or slowest element that took the longest time to load (288 ms) belongs to the original domain Readingpen.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 364 B (45%)

Content Size

805 B

After Optimization

441 B

In fact, the total size of Readingpen.nl main page is 805 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 805 B which makes up the majority of the site volume.

HTML Optimization

-45%

Potential reduce by 364 B

  • Original 805 B
  • After minification 801 B
  • After compression 441 B

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 364 B or 45% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

readingpen.nl accessibility score

93

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

readingpen.nl best practices score

50

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

readingpen.nl SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Readingpen.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Readingpen.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

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