1.9 sec in total
194 ms
1.6 sec
140 ms
Click here to check amazing Api Neo4j content for United States. Otherwise, check out these important facts you probably never knew about api.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 api.neo4j.orgWe analyzed Api.neo4j.org page load time and found that the first response time was 194 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster. This domain responded with an error, which can significantly jeopardize Api.neo4j.org rating and web reputation
api.neo4j.org performance score
194 ms
32 ms
22 ms
10 ms
8 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Api.neo4j.org, 10% (6 requests) were made to Use.typekit.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (497 ms) relates to the external source App-sjl.marketo.com.
Page size can be reduced by 1.5 MB (76%)
2.0 MB
478.3 kB
In fact, the total size of Api.neo4j.org main page is 2.0 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. 70% 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.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 35.1 kB or 78% of the original size.
Potential reduce by 1.6 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. Obviously, Api Neo4j needs image optimization as it can save up to 1.6 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
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. Api.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 (87%)
45
6
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Api 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 6 to 1 for CSS and as a result speed up the page load time.
194 ms
analytics.js
32 ms
prum.min.js
22 ms
wp-emoji-release.min.js
10 ms
cli-style.css
8 ms
font-awesome.min.css
9 ms
app.css
34 ms
codemirror-neo.css
11 ms
download.js
11 ms
jquery-2.2.0.min.js
52 ms
cookielawinfo.js
51 ms
jquery-migrate-1.3.0.min.js
50 ms
modernizr.min.js
51 ms
foundation.min.js
50 ms
codemirror.min.js
54 ms
neo_codemirror.js
54 ms
rdt4xku.js
135 ms
misc.js
53 ms
app.js
53 ms
neo_calculator_v3.js
54 ms
forms2.js
58 ms
munchkin.js
48 ms
d3.min.js
133 ms
json3.min.js
147 ms
neo_d3.js
53 ms
wp-embed.min.js
53 ms
foundation.equalizer.js
53 ms
foundation.clearing.js
56 ms
conversion.js
131 ms
collect
29 ms
foundation-icons.css
27 ms
collect
114 ms
f
122 ms
neo4j-logo-2015.png
299 ms
hr-image.svg
274 ms
search-icon.svg
274 ms
pattern.png
276 ms
neo4j-logo-white.svg
276 ms
p.gif
88 ms
OpenSans-Light-webfont.ttf
84 ms
OpenSans-Regular-webfont.ttf
84 ms
OpenSans-Semibold-webfont.ttf
84 ms
OpenSans-ExtraBold-webfont.ttf
85 ms
fontawesome-webfont.woff
85 ms
QUASAhgHbrWfUvcXAJcUk9TbW4OKkxe7sQH-1IbpgH9ff4aSggM9eMI6MK6f5Mt.eot
86 ms
l2KQ6uk65xaHTWN3D_SH7mH63V8QFowzRsQ3WP92MVGff4DSggM9eMI6MK6f5gI.eot
138 ms
cphQaXSEFscXaQnBkOYIIndGpE3QpYOW7AVTqrSooKvff4_SggM9eMI6MK6f5Mb.eot
138 ms
O52YQfVQuz0Q6UPfPyNr6B0-3A4pJ2O2xpeFjJuXK8Cff4zSggM9eMI6MK6f5MS.eot
138 ms
getForm
497 ms
submit-arrow.svg
26 ms
contact-phone-icon.svg
52 ms
contact-email-icon.svg
55 ms
overlay.png
54 ms
munchkin.js
48 ms
foundation-icons.woff
27 ms
157 ms
visitWebPage
156 ms
44 ms
3153.js
24 ms
api.neo4j.org SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.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 Api.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.
api.neo4j.org
Open Graph data is detected on the main page of Api Neo4j. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: