1.6 sec in total
48 ms
953 ms
562 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 48 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.
neo4j.org performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value9.6 s
0/100
25%
Value8.1 s
21/100
10%
Value2,690 ms
4/100
30%
Value0
100/100
15%
Value15.0 s
8/100
10%
48 ms
52 ms
48 ms
50 ms
43 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Neo4j.org, 41% (31 requests) were made to Dist.neo4j.com and 27% (20 requests) were made to Neo4j.com. The less responsive or slowest element that took the longest time to load (434 ms) relates to the external source Dist.neo4j.com.
Page size can be reduced by 167.0 kB (24%)
707.9 kB
540.9 kB
In fact, the total size of Neo4j.org main page is 707.9 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. 75% 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 451.2 kB which makes up the majority of the site volume.
Potential reduce by 155.5 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 155.5 kB or 80% of the original size.
Potential reduce by 889 B
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, Neo4j needs image optimization as it can save up to 889 B or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 9.4 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.
Potential reduce by 1.2 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 has all CSS files already compressed.
Number of requests can be reduced by 32 (50%)
64
32
The browser has sent 64 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 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
neo4j.org
48 ms
neo4j.org
52 ms
www.neo4j.org
48 ms
www.neo4j.org
50 ms
neo4j.com
43 ms
gtm.js
185 ms
j.php
57 ms
show-login.css
12 ms
hide-login.css
21 ms
jquery.ui.css
20 ms
app.min.css
21 ms
bundle.9cb85.css
37 ms
block-styles.css
38 ms
jquery-3.6.1.min.js
39 ms
settings.js
41 ms
main_v2.min.js
43 ms
language-redirects.min.js
41 ms
animation.css
40 ms
css2
58 ms
dist.min.js
37 ms
imagesloaded.min.js
40 ms
neo_cookies.min.js
42 ms
bundle.13161.js
44 ms
polyfills.03bf6.js
43 ms
set-language-preference.min.js
42 ms
css2
27 ms
v.gif
7 ms
tag-c0b2071df4079775ed3a1f4ec630809e.js
123 ms
Logo_FullColor_RGB_TransBG.svg
253 ms
Icon-GraphAcademy.svg
170 ms
Icon-Documentation.svg
173 ms
Icon-Events.svg
182 ms
gdb.svg
176 ms
auradb.svg
182 ms
genai.svg
170 ms
Logo-GraphSummit.svg
179 ms
Logo-Connections.svg
184 ms
homepage-viz_HERO-BKGD-ART_with-blue.svg
180 ms
homepage-viz_logo-adobe.svg
198 ms
homepage-viz_logo-Novartis-Logo-1.svg
200 ms
homepage-viz_logo-cisco-white-transparent-1.svg
279 ms
homepage-viz_logo-NASA.svg
204 ms
homepage-viz_logo-comcast-white-transparent-2.svg
282 ms
iso-logo-registered-trademark.gif
197 ms
ESG-logo.svg
275 ms
homepage-viz_icon-database-scale.svg
264 ms
homepage-viz_icon-true.svg
274 ms
homepage-viz_Pattern.svg
265 ms
homepage-viz_pattern_375.svg
424 ms
homepage_partners-art.svg
288 ms
homepage-viz_any-cloud_375.svg
287 ms
genai-google-cloud-logo.svg
287 ms
Microsoft_Azure_Logo-1.png
286 ms
genai-aws-logo.svg
427 ms
homepage-viz_ART-left.svg
421 ms
homepage-viz_ART-right.svg
418 ms
homepage-viz_left-side-art_375.svg
425 ms
homepage-viz_right-side-art_375.svg
426 ms
icon-tooltip-info.svg
434 ms
tag-ac4fdae44fa7b0fa6c310253ae309fea.js
175 ms
settings.js
139 ms
js
213 ms
uc.js
359 ms
destination
195 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpm5wA.woff
126 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuSJm5wA.woff
271 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuyJ65wA.woff
287 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymu8Z65wA.woff
288 ms
SyneNeo-Medium.woff
31 ms
SyneNeo-Medium.woff
13 ms
worker-70faafffa0475802f5ee03ca5ff74179.js
197 ms
s.gif
171 ms
s.gif
30 ms
s.gif
46 ms
settings.js
39 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
[role] values are not valid
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
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: