1.6 sec in total
25 ms
1.1 sec
454 ms
Click here to check amazing Docs Neo4j content for United States. Otherwise, check out these important facts you probably never knew about docs.neo4j.org
Read the latest Neo4j documentation to learn all you need to about Neo4j and graph databases, and start building your first graph database application.
Visit docs.neo4j.orgWe analyzed Docs.neo4j.org page load time and found that the first response time was 25 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
docs.neo4j.org performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value5.1 s
26/100
25%
Value4.2 s
78/100
10%
Value1,020 ms
26/100
30%
Value0
100/100
15%
Value11.2 s
20/100
10%
25 ms
209 ms
33 ms
29 ms
13 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Docs.neo4j.org, 63% (37 requests) were made to Neo4j.com and 5% (3 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (361 ms) relates to the external source App-sjl.marketo.com.
Page size can be reduced by 1.5 MB (68%)
2.2 MB
713.4 kB
In fact, the total size of Docs.neo4j.org main page is 2.2 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. 65% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 35.6 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 35.6 kB or 77% of the original size.
Potential reduce by 23.5 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. Docs Neo4j images are well optimized though.
Potential reduce by 1.2 MB
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 1.2 MB or 74% of the original size.
Potential reduce by 261.1 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. Docs.neo4j.org needs all CSS files to be minified and compressed as it can save up to 261.1 kB or 85% of the original size.
Number of requests can be reduced by 39 (78%)
50
11
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docs Neo4j. 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 5 to 1 for CSS and as a result speed up the page load time.
docs.neo4j.org
25 ms
209 ms
analytics.js
33 ms
prum.min.js
29 ms
wp-emoji-release.min.js
13 ms
cli-style.css
13 ms
font-awesome.min.css
14 ms
app.css
41 ms
codemirror-neo.css
16 ms
download.js
39 ms
jquery-2.2.0.min.js
54 ms
cookielawinfo.js
38 ms
jquery-migrate-1.3.0.min.js
37 ms
modernizr.min.js
37 ms
foundation.min.js
70 ms
codemirror.min.js
63 ms
neo_codemirror.js
53 ms
rdt4xku.js
178 ms
misc.js
53 ms
app.js
66 ms
neo_calculator_v3.js
66 ms
forms2.js
65 ms
munchkin.js
34 ms
d3.min.js
174 ms
json3.min.js
173 ms
neo_d3.js
64 ms
wp-embed.min.js
63 ms
foundation.equalizer.js
64 ms
foundation.clearing.js
171 ms
conversion.js
63 ms
foundation-icons.css
32 ms
collect
314 ms
neo4j-logo-2015.png
177 ms
icon-developer.png
211 ms
hr-image.svg
158 ms
cropped-graphdatabases_cover390x5121.png
201 ms
neo4j20_de_large.jpg
200 ms
Learning_Neo4j_Cover-129x150.gif
197 ms
search-icon.svg
190 ms
pattern-left-100.png
193 ms
neo4j-logo-white.svg
191 ms
OpenSans-Light-webfont.ttf
194 ms
OpenSans-Regular-webfont.ttf
194 ms
OpenSans-Semibold-webfont.ttf
194 ms
OpenSans-ExtraBold-webfont.ttf
194 ms
fontawesome-webfont.woff
43 ms
getForm
361 ms
submit-arrow.svg
17 ms
contact-phone-icon.svg
56 ms
contact-email-icon.svg
56 ms
overlay.png
58 ms
munchkin.js
52 ms
157 ms
foundation-icons.woff
125 ms
visitWebPage
202 ms
3153.js
26 ms
71 ms
s
92 ms
u
54 ms
docs.neo4j.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
docs.neo4j.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
docs.neo4j.org SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docs.neo4j.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Docs.neo4j.org 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.
docs.neo4j.org
Open Graph data is detected on the main page of Docs Neo4j. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: