2.3 sec in total
25 ms
1.7 sec
523 ms
Click here to check amazing Gist Neo4j content for United States. Otherwise, check out these important facts you probably never knew about gist.neo4j.org
Learn how to model & explore data as a graph for your use case or industry.
Visit gist.neo4j.orgWe analyzed Gist.neo4j.org page load time and found that the first response time was 25 ms and then it took 2.2 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.
gist.neo4j.org performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value3.9 s
53/100
25%
Value3.5 s
88/100
10%
Value280 ms
80/100
30%
Value0.003
100/100
15%
Value12.1 s
16/100
10%
25 ms
20 ms
15 ms
67 ms
15 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gist.neo4j.org, 38% (40 requests) were made to Neo4j.com and 31% (33 requests) were made to Graphgist-portal-production.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (982 ms) relates to the external source Graphgist-portal-production.s3.amazonaws.com.
Page size can be reduced by 1.9 MB (70%)
2.7 MB
820.3 kB
In fact, the total size of Gist.neo4j.org main page is 2.7 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. 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 44.6 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.6 kB or 77% of the original size.
Potential reduce by 56.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. Obviously, Gist Neo4j needs image optimization as it can save up to 56.3 kB or 24% 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.5 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.5 MB or 72% of the original size.
Potential reduce by 292.7 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. Gist.neo4j.org needs all CSS files to be minified and compressed as it can save up to 292.7 kB or 84% of the original size.
Number of requests can be reduced by 49 (53%)
92
43
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gist 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 9 to 1 for CSS and as a result speed up the page load time.
gist.neo4j.org
25 ms
20 ms
jquery.min.js
15 ms
cli-style.css
67 ms
font-awesome.min.css
15 ms
app.css
70 ms
codemirror-neo.css
13 ms
download.js
11 ms
jquery-2.2.0.min.js
63 ms
cookielawinfo.js
62 ms
jquery-migrate-1.3.0.min.js
66 ms
modernizr.min.js
62 ms
foundation.min.js
108 ms
codemirror.min.js
62 ms
neo_codemirror.js
109 ms
rdt4xku.js
254 ms
misc.js
105 ms
bundle.js
108 ms
neo_calculator_v3.js
63 ms
graphgists.css
106 ms
foundation.equalizer.min.js
108 ms
forms2.js
61 ms
d3.min.js
243 ms
json3.min.js
243 ms
neo_d3.js
128 ms
wp-embed.min.js
126 ms
foundation.equalizer.js
127 ms
foundation.clearing.js
126 ms
conversion.js
105 ms
analytics.js
76 ms
prum.min.js
81 ms
wp-emoji-release.min.js
79 ms
foundation-icons.css
67 ms
collect
127 ms
collect
67 ms
neo4j.com
133 ms
neo4j-logo-2015.png
115 ms
noun_22440-green-02.png
95 ms
noun_11084.png
220 ms
noun_176315.png
211 ms
noun_358410.png
254 ms
noun_252754.png
255 ms
noun_62765.png
254 ms
noun_253701.png
254 ms
noun_258963.png
360 ms
noun_11925.png
587 ms
graph_search_icon.png
640 ms
noun_401.png
585 ms
noun_106914.png
585 ms
noun_301197.png
588 ms
noun_107281.png
587 ms
noun_358752.png
766 ms
noun_38252.png
768 ms
noun_228021.png
764 ms
noun_145195.png
866 ms
noun_361203.png
765 ms
noun_12737.png
820 ms
noun_129319.png
865 ms
noun_94092.png
868 ms
noun_31439.png
867 ms
noun_105235.png
866 ms
noun_10993.png
982 ms
noun_10191.png
941 ms
noun_144785.png
942 ms
noun_87003.png
943 ms
open-uri20151208-3-aharqv
714 ms
open-uri20151208-3-1r5ble1
867 ms
open-uri20151208-3-1s2nvy3
864 ms
open-uri20151208-3-1qj3xfw
762 ms
open-uri20151208-3-u0es3d
765 ms
open-uri20151208-3-7yibog
863 ms
search-icon.svg
77 ms
pattern-left-100.png
78 ms
hr-image.svg
11 ms
neo4j-logo-white.svg
125 ms
OpenSans-Light-webfont.ttf
122 ms
OpenSans-Regular-webfont.ttf
121 ms
OpenSans-Semibold-webfont.ttf
119 ms
OpenSans-ExtraBold-webfont.ttf
120 ms
getForm
434 ms
submit-arrow.svg
6 ms
fontawesome-webfont.woff
103 ms
contact-phone-icon.svg
101 ms
contact-email-icon.svg
98 ms
overlay.png
99 ms
288 ms
foundation-icons.woff
234 ms
munchkin.js
219 ms
3153.js
37 ms
kh-t-VoY4XNIdJoHpMfNYCJekFemqj5_QzSUZuDYdG6ff4aSggMdeMJ6Mk6f5Mt.woff
57 ms
liQ86ZPHX_Q7gdkAmnC9XkG1vI07DKP9QAZ0wE0j5Hjff4DSggMdeMJ6Mk6f5gI.woff
101 ms
sVdhdzRxYn0zDzSoTIxGApFg2_p7UXT7yzwWx3LeDu6ff4_SggMdeMJ6Mk6f5Mb.woff
183 ms
9wVbVw8xSH_mLkG_iaA8QnidUnvHTMv6P6mTiUsOlf3ff4zSggMdeMJ6Mk6f5MS.woff
240 ms
munchkin.js
44 ms
126 ms
s
195 ms
u
282 ms
visitWebPage
198 ms
forms2.css
82 ms
forms2-theme-simple.css
80 ms
p.gif
126 ms
XDFrame
223 ms
inspectlet.js
10 ms
656443939
68 ms
beacon.gif
39 ms
forms2.min.js
11 ms
gist.neo4j.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
gist.neo4j.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
gist.neo4j.org SEO score
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 Gist.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 Gist.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.
gist.neo4j.org
Open Graph data is detected on the main page of Gist Neo4j. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: