3.4 sec in total
90 ms
2.4 sec
889 ms
Visit neo4j.org now to see the best up-to-date Neo4j content for United States and also check out these interesting facts you probably never knew about neo4j.org
Connect data as it's stored with Neo4j. Perform powerful, complex queries at scale and speed with our graph data platform.
Visit neo4j.orgWe analyzed Neo4j.org page load time and found that the first response time was 90 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
neo4j.org performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value13.6 s
0/100
25%
Value46.8 s
0/100
10%
Value52,370 ms
0/100
30%
Value0
100/100
15%
Value79.5 s
0/100
10%
90 ms
80 ms
75 ms
45 ms
45 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Neo4j.org, 21% (20 requests) were made to S3.amazonaws.com and 6% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (809 ms) relates to the external source 773-gon-065.mktoresp.com.
Page size can be reduced by 1.8 MB (51%)
3.6 MB
1.8 MB
In fact, the total size of Neo4j.org main page is 3.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 44.8 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 44.8 kB or 76% of the original size.
Potential reduce by 69.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. Neo4j images are well optimized though.
Potential reduce by 1.4 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.4 MB or 73% of the original size.
Potential reduce by 283.5 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. Neo4j.org needs all CSS files to be minified and compressed as it can save up to 283.5 kB or 85% of the original size.
Number of requests can be reduced by 51 (61%)
84
33
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 31 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
neo4j.com
90 ms
analytics.js
80 ms
prum.min.js
75 ms
wp-emoji-release.min.js
45 ms
cli-style.css
45 ms
font-awesome.min.css
49 ms
app.css
79 ms
codemirror-neo.css
64 ms
download.js
59 ms
jquery-2.2.0.min.js
121 ms
cookielawinfo.js
119 ms
jquery-migrate-1.3.0.min.js
146 ms
modernizr.min.js
118 ms
foundation.min.js
148 ms
codemirror.min.js
143 ms
neo_codemirror.js
141 ms
rdt4xku.js
270 ms
misc.js
136 ms
bundle.js
138 ms
neo_calculator_v3.js
140 ms
forms2.js
260 ms
d3.min.js
298 ms
json3.min.js
327 ms
neo_d3.js
131 ms
home-events.js
132 ms
home.js
131 ms
wp-embed.min.js
130 ms
foundation.equalizer.js
131 ms
foundation.clearing.js
131 ms
conversion.js
279 ms
foundation-icons.css
80 ms
collect
176 ms
neo4j.com
137 ms
collect
65 ms
neo4j-logo-2015.png
113 ms
neo4j-2.3-banner.jpg
457 ms
neo4j-2.3-arrow-down.png
428 ms
neo4j-2.3-screen-asset.png
428 ms
gc-europe-banner.jpg
447 ms
gc-london-logo-round.png
426 ms
rdbms2GDB-3.jpg
450 ms
graph-database-guide-rdbms-developer.png
434 ms
learn-bg.png
437 ms
GDB-2e-cover.jpg
454 ms
thumbnail-getting-started-cropped.png
452 ms
opencypher-slider-banner.jpg
450 ms
opencypher-slider-asset.png
443 ms
pitney-bowes-150x71.png
442 ms
diebayerische.png
447 ms
ICIJ-340x160-150x71.png
443 ms
Schleich-logo-150x38.png
443 ms
ebay.png
445 ms
walmart-150x41.png
445 ms
global-2000-adidas-150x71.png
445 ms
telenor.png
449 ms
search-icon.svg
190 ms
new-to-graphs-icon-prompts.svg
187 ms
new-to-graphs-icon-document.svg
194 ms
new-to-graphs-icon-chart.svg
195 ms
spacer-img.png
192 ms
text-balloon-tick.svg
197 ms
neo4j-logo-white.svg
199 ms
OpenSans-Light-webfont.ttf
358 ms
OpenSans-Regular-webfont.ttf
358 ms
OpenSans-Semibold-webfont.ttf
357 ms
OpenSans-ExtraBold-webfont.ttf
136 ms
fontawesome-webfont.woff
358 ms
getForm
495 ms
submit-arrow.svg
140 ms
contact-phone-icon.svg
129 ms
contact-email-icon.svg
134 ms
overlay.png
134 ms
355 ms
slide-arrow.svg
116 ms
foundation-icons.woff
300 ms
munchkin.js
227 ms
events.json
69 ms
232 ms
event-conference.png
86 ms
3153.js
172 ms
kh-t-VoY4XNIdJoHpMfNYCJekFemqj5_QzSUZuDYdG6ff4aSggMdeMJ6Mk6f5Mt.woff
172 ms
liQ86ZPHX_Q7gdkAmnC9XkG1vI07DKP9QAZ0wE0j5Hjff4DSggMdeMJ6Mk6f5gI.woff
301 ms
sVdhdzRxYn0zDzSoTIxGApFg2_p7UXT7yzwWx3LeDu6ff4_SggMdeMJ6Mk6f5Mb.woff
303 ms
9wVbVw8xSH_mLkG_iaA8QnidUnvHTMv6P6mTiUsOlf3ff4zSggMdeMJ6Mk6f5MS.woff
303 ms
event-webinar.png
77 ms
munchkin.js
47 ms
forms2.css
47 ms
forms2-theme-simple.css
49 ms
visitWebPage
809 ms
inspectlet.js
86 ms
s
288 ms
u
266 ms
XDFrame
356 ms
p.gif
293 ms
beacon.gif
260 ms
656443939
109 ms
forms2.min.js
12 ms
neo4j.org accessibility score
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
[aria-*] attributes do not match their roles
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
neo4j.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 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 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.
neo4j.org
Open Graph data is detected on the main page of Neo4j. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: