2.2 sec in total
51 ms
1.5 sec
586 ms
Visit neo4j.com now to see the best up-to-date Neo4j content for China and also check out these interesting facts you probably never knew about neo4j.com
Connect data as it's stored with Neo4j. Perform powerful, complex queries at scale and speed with our graph data platform.
Visit neo4j.comWe analyzed Neo4j.com page load time and found that the first response time was 51 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
neo4j.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value9.8 s
0/100
25%
Value4.2 s
77/100
10%
Value2,480 ms
4/100
30%
Value0
100/100
15%
Value11.9 s
16/100
10%
51 ms
33 ms
31 ms
12 ms
11 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 37% of them (37 requests) were addressed to the original Neo4j.com, 23% (23 requests) were made to Dev.assets.neo4j.com.s3.amazonaws.com and 8% (8 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (568 ms) relates to the external source Dev.assets.neo4j.com.s3.amazonaws.com.
Page size can be reduced by 1.9 MB (55%)
3.4 MB
1.5 MB
In fact, the total size of Neo4j.com main page is 3.4 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 49.2 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 49.2 kB or 77% of the original size.
Potential reduce by 106.3 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 272.9 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.com needs all CSS files to be minified and compressed as it can save up to 272.9 kB or 85% of the original size.
Number of requests can be reduced by 45 (52%)
86
41
The browser has sent 86 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 29 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
neo4j.com
51 ms
analytics.js
33 ms
prum.min.js
31 ms
wp-emoji-release.min.js
12 ms
cli-style.css
11 ms
font-awesome.min.css
12 ms
app.css
35 ms
codemirror-neo.css
13 ms
download.js
50 ms
jquery-2.2.0.min.js
34 ms
cookielawinfo.js
49 ms
jquery-migrate-1.3.0.min.js
49 ms
modernizr.min.js
49 ms
foundation.min.js
50 ms
codemirror.min.js
52 ms
neo_codemirror.js
52 ms
rdt4xku.js
165 ms
misc.js
52 ms
app.js
51 ms
neo_calculator_v3.js
51 ms
forms2.js
50 ms
munchkin.js
53 ms
d3.min.js
282 ms
json3.min.js
284 ms
neo_d3.js
49 ms
wp-embed.min.js
52 ms
foundation.equalizer.js
52 ms
foundation.clearing.js
50 ms
conversion.js
160 ms
collect
29 ms
foundation-icons.css
24 ms
collect
385 ms
neo4j-logo-2015.png
97 ms
neo4j-2.3-banner.jpg
224 ms
hr-image.svg
164 ms
lufthansa.png
209 ms
ebay.png
209 ms
diebayerische.png
213 ms
onefinestay.png
210 ms
Roposo-340x160.png
208 ms
pitney-bowes.png
211 ms
walmart.png
209 ms
tomtom.png
210 ms
search-icon.svg
190 ms
neo4j-2.3-arrow-down.png
362 ms
neo4j-2.3-slide-asset.png
212 ms
opencypher-slider-banner.jpg
214 ms
opencypher-slider-asset.png
264 ms
power8-slider-banner.png
568 ms
power8-banner-asset.png
212 ms
twitter-header-bg.gif
213 ms
twitter-browser-demo.gif
213 ms
rdbms2GDB-3.jpg
266 ms
WP-OverComing-SQL-Strain.png
214 ms
infojobs-logo_340x160.png
214 ms
global-2000-adidas.png
264 ms
global-500-logistics.png
267 ms
pitney-bowes.png
263 ms
megree.png
264 ms
wazoku.png
265 ms
graph-database-circle.png
297 ms
learn-neo4j-circle.png
266 ms
online-course-circle.png
296 ms
320px-EBay_logo.png
297 ms
walmart.png
298 ms
telenor.png
358 ms
OpenSans-Light-webfont.ttf
186 ms
OpenSans-Regular-webfont.ttf
201 ms
OpenSans-Semibold-webfont.ttf
187 ms
OpenSans-ExtraBold-webfont.ttf
187 ms
events.json
152 ms
neo4j-logo-white.svg
140 ms
fontawesome-webfont.woff
36 ms
getForm
350 ms
submit-arrow.svg
3 ms
contact-phone-icon.svg
49 ms
contact-email-icon.svg
51 ms
overlay.png
50 ms
munchkin.js
45 ms
foundation-icons.woff
16 ms
192 ms
visitWebPage
190 ms
95 ms
3153.js
7 ms
s
47 ms
u
50 ms
forms2.css
8 ms
forms2-theme-simple.css
10 ms
inspectlet.js
23 ms
beacon.gif
323 ms
656443939
91 ms
XDFrame
348 ms
getfid
22 ms
getfid
162 ms
fa
139 ms
fa
139 ms
fa
5 ms
fa
5 ms
forms2.min.js
11 ms
neo4j.com 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
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.com 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.com 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
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.com 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.com 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.com
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: