3.8 sec in total
432 ms
2.6 sec
793 ms
Click here to check amazing Info Neo4j content for China. Otherwise, check out these important facts you probably never knew about info.neo4j.com
Connect data as it's stored with Neo4j. Perform powerful, complex queries at scale and speed with our graph data platform.
Visit info.neo4j.comWe analyzed Info.neo4j.com page load time and found that the first response time was 432 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
info.neo4j.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value8.5 s
2/100
25%
Value6.4 s
40/100
10%
Value3,140 ms
2/100
30%
Value0.044
99/100
15%
Value14.8 s
8/100
10%
432 ms
74 ms
64 ms
58 ms
34 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Info.neo4j.com, 47% (46 requests) were made to Neo4j.com and 20% (20 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (878 ms) relates to the external source S3.amazonaws.com.
Page size can be reduced by 1.8 MB (50%)
3.6 MB
1.8 MB
In fact, the total size of Info.neo4j.com 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 45.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 45.5 kB or 76% of the original size.
Potential reduce by 70.4 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. Info 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 72% 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. Info.neo4j.com 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 Info 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.
info.neo4j.com
432 ms
neo4j.com
74 ms
analytics.js
64 ms
prum.min.js
58 ms
wp-emoji-release.min.js
34 ms
cli-style.css
32 ms
font-awesome.min.css
34 ms
app.css
42 ms
codemirror-neo.css
36 ms
download.js
73 ms
jquery-2.2.0.min.js
73 ms
cookielawinfo.js
35 ms
jquery-migrate-1.3.0.min.js
37 ms
modernizr.min.js
35 ms
foundation.min.js
154 ms
codemirror.min.js
93 ms
neo_codemirror.js
90 ms
rdt4xku.js
234 ms
misc.js
89 ms
bundle.js
89 ms
neo_calculator_v3.js
89 ms
forms2.js
84 ms
d3.min.js
221 ms
json3.min.js
225 ms
neo_d3.js
86 ms
home-events.js
86 ms
home.js
85 ms
wp-embed.min.js
85 ms
foundation.equalizer.js
88 ms
foundation.clearing.js
142 ms
conversion.js
142 ms
foundation-icons.css
66 ms
collect
150 ms
collect
50 ms
neo4j.com
128 ms
neo4j-logo-2015.png
141 ms
neo4j-2.3-banner.jpg
758 ms
neo4j-2.3-arrow-down.png
245 ms
neo4j-2.3-screen-asset.png
245 ms
gc-europe-banner.jpg
790 ms
gc-london-logo-round.png
244 ms
rdbms2GDB-3.jpg
878 ms
graph-database-guide-rdbms-developer.png
732 ms
learn-bg.png
874 ms
GDB-2e-cover.jpg
241 ms
thumbnail-getting-started-cropped.png
729 ms
opencypher-slider-banner.jpg
874 ms
opencypher-slider-asset.png
449 ms
diebayerische.png
448 ms
ICIJ-340x160-150x71.png
448 ms
global-2000-adidas-150x71.png
447 ms
Schleich-logo-150x38.png
785 ms
gamesys-150x71.png
784 ms
cerved-neo4j-case-study-150x40.png
789 ms
ebay.png
787 ms
pitney-bowes-150x71.png
873 ms
search-icon.svg
97 ms
new-to-graphs-icon-prompts.svg
107 ms
new-to-graphs-icon-document.svg
103 ms
new-to-graphs-icon-chart.svg
232 ms
spacer-img.png
238 ms
text-balloon-tick.svg
105 ms
neo4j-logo-white.svg
236 ms
OpenSans-Light-webfont.ttf
208 ms
OpenSans-Regular-webfont.ttf
352 ms
OpenSans-Semibold-webfont.ttf
349 ms
OpenSans-ExtraBold-webfont.ttf
350 ms
fontawesome-webfont.woff
628 ms
getForm
596 ms
submit-arrow.svg
480 ms
contact-phone-icon.svg
376 ms
contact-email-icon.svg
370 ms
overlay.png
433 ms
454 ms
slide-arrow.svg
342 ms
foundation-icons.woff
347 ms
munchkin.js
382 ms
events.json
207 ms
3153.js
81 ms
kh-t-VoY4XNIdJoHpMfNYCJekFemqj5_QzSUZuDYdG6ff4aSggMdeMJ6Mk6f5Mt.woff
127 ms
liQ86ZPHX_Q7gdkAmnC9XkG1vI07DKP9QAZ0wE0j5Hjff4DSggMdeMJ6Mk6f5gI.woff
129 ms
sVdhdzRxYn0zDzSoTIxGApFg2_p7UXT7yzwWx3LeDu6ff4_SggMdeMJ6Mk6f5Mb.woff
241 ms
9wVbVw8xSH_mLkG_iaA8QnidUnvHTMv6P6mTiUsOlf3ff4zSggMdeMJ6Mk6f5MS.woff
360 ms
285 ms
event-training.png
75 ms
munchkin.js
176 ms
forms2.css
160 ms
forms2-theme-simple.css
218 ms
event-meetup.png
159 ms
s
210 ms
u
200 ms
visitWebPage
317 ms
inspectlet.js
53 ms
p.gif
187 ms
beacon.gif
156 ms
XDFrame
271 ms
656443939
65 ms
forms2.min.js
10 ms
info.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
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
info.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
info.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 Info.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 Info.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.
info.neo4j.com
Open Graph data is detected on the main page of Info Neo4j. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: