Tools & Wizards About Us
nextdoor.nl screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

nextdoor.nl

Nextdoor

Page Load Speed

2.9 sec in total

First Response

179 ms

Resources Loaded

2.1 sec

Page Rendered

631 ms

nextdoor.nl screenshot

About Website

Visit nextdoor.nl now to see the best up-to-date Nextdoor content for Netherlands and also check out these interesting facts you probably never knew about nextdoor.nl

Join Nextdoor, an app for neighborhoods where you can get local tips, buy and sell items, and more

Visit nextdoor.nl

Key Findings

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

Performance Metrics

nextdoor.nl performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.6 s

0/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value4,880 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value27.8 s

0/100

10%

Network Requests Diagram

nextdoor.nl

179 ms

nextdoor.nl

529 ms

bootstrap.css

69 ms

responsive.css

81 ms

main.css

103 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 6% of them (4 requests) were addressed to the original Nextdoor.nl, 69% (47 requests) were made to D19rpgkrjeba2z.cloudfront.net and 7% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (529 ms) belongs to the original domain Nextdoor.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 771.7 kB (26%)

Content Size

2.9 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 46.8 kB

  • Original 63.0 kB
  • After minification 57.4 kB
  • After compression 16.1 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 46.8 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 29.5 kB

  • Original 1.9 MB
  • After minification 1.9 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. Nextdoor images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 305.2 kB

  • Original 495.3 kB
  • After minification 495.3 kB
  • After compression 190.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 305.2 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 390.2 kB

  • Original 469.2 kB
  • After minification 462.7 kB
  • After compression 79.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. Nextdoor.nl needs all CSS files to be minified and compressed as it can save up to 390.2 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

62

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nextdoor.nl

nextdoor.nl

179 ms

nextdoor.nl

nextdoor.nl

529 ms

bootstrap.css

bootstrap.css

69 ms

responsive.css

responsive.css

81 ms

main.css

main.css

103 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

129 ms

select2.css

select2.css

119 ms

compose.css

compose.css

79 ms

fonts.css

fonts.css

91 ms

signup-tests-fonts.css

signup-tests-fonts.css

89 ms

signup.css

signup.css

121 ms

footer.css

footer.css

127 ms

vendor.js

vendor.js

148 ms

jquery.min.js

jquery.min.js

199 ms

bootstrap.min.js

bootstrap.min.js

124 ms

base.js

base.js

135 ms

js

js

252 ms

jquery_autocomplete.min.js

jquery_autocomplete.min.js

123 ms

mailcheck.js

mailcheck.js

291 ms

user_name_filter.js

user_name_filter.js

134 ms

AddressEntry.js

AddressEntry.js

132 ms

signup.js

signup.js

129 ms

validateEmail.js

validateEmail.js

130 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

183 ms

utils.js

utils.js

181 ms

SimpleMap.js

SimpleMap.js

184 ms

GeoJSON.js

GeoJSON.js

181 ms

infobox.js

infobox.js

183 ms

selfGeocode.js

selfGeocode.js

184 ms

fp.js

fp.js

161 ms

badge_google@2x.png

badge_google@2x.png

113 ms

badge_apple@2x.png

badge_apple@2x.png

65 ms

press_desktop_sm@2x.png

press_desktop_sm@2x.png

158 ms

press_responsive@2x.png

press_responsive@2x.png

121 ms

icon-lock@2x.png

icon-lock@2x.png

159 ms

icon-phone@2x.png

icon-phone@2x.png

113 ms

icon-neighborhood@2x.png

icon-neighborhood@2x.png

160 ms

icon-playvideo@2x.png

icon-playvideo@2x.png

119 ms

productgroup_350px@2x.jpg

productgroup_350px@2x.jpg

252 ms

iphone@2x.png

iphone@2x.png

305 ms

TestimonialGabi@2x.jpg

TestimonialGabi@2x.jpg

312 ms

paulien@2x.jpg

paulien@2x.jpg

252 ms

jasper2.jpg

jasper2.jpg

407 ms

twitter-white@2x.png

twitter-white@2x.png

244 ms

facebook-white@2x.png

facebook-white@2x.png

305 ms

analytics.js

analytics.js

168 ms

214 ms

sdk.js

sdk.js

142 ms

0

0

304 ms

common.js

common.js

76 ms

util.js

util.js

173 ms

controls.js

controls.js

157 ms

places_impl.js

places_impl.js

173 ms

powered_by_google_on_white.png

powered_by_google_on_white.png

208 ms

offsite_event.php

offsite_event.php

188 ms

cEy.js

cEy.js

184 ms

collect

collect

62 ms

collect

collect

130 ms

422 ms

65a79b5

65a79b5

15 ms

hero_bikes_web.jpg

hero_bikes_web.jpg

104 ms

map@2x_optimized.jpg

map@2x_optimized.jpg

150 ms

dutchhousesillustrations1.png

dutchhousesillustrations1.png

68 ms

ndicons.woff

ndicons.woff

10 ms

ss-standard.woff

ss-standard.woff

18 ms

nr-885.min.js

nr-885.min.js

55 ms

xd_arbiter.php

xd_arbiter.php

131 ms

b55be5e15c

b55be5e15c

100 ms

Accessibility Review

nextdoor.nl accessibility score

83

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

button, link, and menuitem elements do not have accessible names.

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

Form elements do not have associated labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Page has valid source maps

SEO Factors

nextdoor.nl SEO score

85

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    EN

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

nextdoor.nl

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