Tools & Wizards About Us
faketekst.nl screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

faketekst.nl

Faketekst / Lorem Ipsum / Voorbeeldtekst / Dummytekst genereren

Page Load Speed

2.3 sec in total

First Response

369 ms

Resources Loaded

1.8 sec

Page Rendered

121 ms

faketekst.nl screenshot

About Website

Click here to check amazing Faketekst content for Netherlands. Otherwise, check out these important facts you probably never knew about faketekst.nl

Faketekst.nl is de website voor een faketekst, lorem ipsum, voorbeeldtekst of dummytekst voor drukwerk of webdesign. Kopieer en gebruik!

Visit faketekst.nl

Key Findings

We analyzed Faketekst.nl page load time and found that the first response time was 369 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

faketekst.nl performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.199

62/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

faketekst.nl

369 ms

www.faketekst.nl

492 ms

css

36 ms

style.css

96 ms

cookieconsent.css

191 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 27% of them (8 requests) were addressed to the original Faketekst.nl, 33% (10 requests) were made to Static.xx.fbcdn.net and 10% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (537 ms) belongs to the original domain Faketekst.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 27.0 kB (5%)

Content Size

490.2 kB

After Optimization

463.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Faketekst.nl main page is 490.2 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. 40% of websites need less resources to load. Javascripts take 287.2 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 25.2 kB

  • Original 42.1 kB
  • After minification 42.1 kB
  • After compression 16.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 25.2 kB or 60% of the original size.

Image Optimization

-1%

Potential reduce by 1.3 kB

  • Original 158.0 kB
  • After minification 156.7 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. Faketekst images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 92 B

  • Original 287.2 kB
  • After minification 287.2 kB
  • After compression 287.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 315 B

  • Original 2.9 kB
  • After minification 2.9 kB
  • After compression 2.6 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. Faketekst.nl needs all CSS files to be minified and compressed as it can save up to 315 B or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (56%)

Requests Now

27

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faketekst. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

faketekst.nl

faketekst.nl

369 ms

www.faketekst.nl

www.faketekst.nl

492 ms

css

css

36 ms

style.css

style.css

96 ms

cookieconsent.css

cookieconsent.css

191 ms

adsbygoogle.js

adsbygoogle.js

177 ms

js

js

49 ms

includen.js

includen.js

537 ms

likebox.php

likebox.php

262 ms

toolmenubg.png

toolmenubg.png

116 ms

faketekstbg.jpg

faketekstbg.jpg

515 ms

logo.png

logo.png

210 ms

show_ads_impl.js

show_ads_impl.js

314 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

16 ms

e0qhfylH8yR.css

e0qhfylH8yR.css

12 ms

sGqMB8s6FJy.js

sGqMB8s6FJy.js

18 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

17 ms

s23ZuKml3wQ.js

s23ZuKml3wQ.js

41 ms

XYkWt7jI7LC.js

XYkWt7jI7LC.js

46 ms

_uEhsxKAS3c.js

_uEhsxKAS3c.js

45 ms

9f_Alkp5qWb.js

9f_Alkp5qWb.js

45 ms

p55HfXW__mM.js

p55HfXW__mM.js

44 ms

301197679_171799628735860_4684302630435843057_n.jpg

301197679_171799628735860_4684302630435843057_n.jpg

86 ms

301206864_171799625402527_2603152996376836553_n.jpg

301206864_171799625402527_2603152996376836553_n.jpg

86 ms

8KaDrtfF0aP.js

8KaDrtfF0aP.js

75 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

33 ms

zrt_lookup.html

zrt_lookup.html

42 ms

ads

ads

272 ms

ads

ads

77 ms

ca-pub-8273329267089581

ca-pub-8273329267089581

74 ms

Accessibility Review

faketekst.nl accessibility score

87

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

Form elements do not have associated labels

Best Practices

faketekst.nl best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

faketekst.nl SEO score

92

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

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

faketekst.nl

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