5.7 sec in total
212 ms
4.4 sec
1.1 sec
Click here to check amazing Gora Apache content for China. Otherwise, check out these important facts you probably never knew about gora.apache.org
Apache Gora -- Welcome to Apache Gora™
Visit gora.apache.orgWe analyzed Gora.apache.org page load time and found that the first response time was 212 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
gora.apache.org performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value2.8 s
82/100
25%
Value4.8 s
68/100
10%
Value1,980 ms
8/100
30%
Value0
100/100
15%
Value14.5 s
9/100
10%
212 ms
179 ms
167 ms
166 ms
40 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 9% of them (11 requests) were addressed to the original Gora.apache.org, 9% (12 requests) were made to Public.slidesharecdn.com and 9% (12 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Rs.gwallet.com.
Page size can be reduced by 2.8 MB (73%)
3.8 MB
1.0 MB
In fact, the total size of Gora.apache.org main page is 3.8 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.7 MB which makes up the majority of the site volume.
Potential reduce by 35.1 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 35.1 kB or 72% of the original size.
Potential reduce by 126.8 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, Gora Apache needs image optimization as it can save up to 126.8 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 2.2 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 2.2 MB or 81% of the original size.
Potential reduce by 468.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. Gora.apache.org needs all CSS files to be minified and compressed as it can save up to 468.5 kB or 82% of the original size.
Number of requests can be reduced by 59 (52%)
114
55
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gora Apache. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
gora.apache.org
212 ms
bootstrap.css
179 ms
bootstrap-responsive.css
167 ms
gora.css
166 ms
buttons.js
40 ms
loader.js
7 ms
brand
16 ms
jquery.min.js
35 ms
bootstrap.min.js
169 ms
brand
34 ms
widgets.js
148 ms
Open-Catalog-Single-Big.png
248 ms
mongodb-logo.png
149 ms
apache-camel-100h.png
637 ms
hbase_logo.png
282 ms
OSD_logo.png
243 ms
ApacheGiraph.svg
570 ms
33495268
242 ms
EU_speaker_wide_25.png
449 ms
pulldownbar.063710b50056a153b27845a5970365c7.css
124 ms
pulldownbar.563f805066c86e220f7fa3df63b0da80.js
129 ms
google_custom_search_watermark.gif
215 ms
getAllAppDefault.esi
183 ms
gora-logo.png
218 ms
feather-small.png
132 ms
tcube.jpeg
129 ms
gsoc2013.jpg
216 ms
hadoopsphere.png
275 ms
gsoc2012.jpg
494 ms
mongodb-logo.png
179 ms
426 ms
442 ms
485 ms
483 ms
06PjlHJ2srY
235 ms
481 ms
419 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
105 ms
DRlfSbSfVC4
217 ms
Ps-j4aro99U
216 ms
combined_jquery.js
118 ms
global.js
149 ms
combined_li_tracking.js
118 ms
font-awesome.css
116 ms
combined_presentation.css
163 ms
combined_player_presentation.js
186 ms
combined_old_embed.js
220 ms
syndication
407 ms
473948188378812419
477 ms
getSegment.php
75 ms
checkOAuth.esi
68 ms
combined_base.js
260 ms
www-embed-player-vflfNyN_r.css
444 ms
www-embed-player.js
516 ms
ga.js
305 ms
beacon.js
307 ms
t.dhj
353 ms
giraphgora-in-apachecon14-1-638.jpg
544 ms
33495268
229 ms
1x1.gif
230 ms
logo_embed_20x20_v1.png
230 ms
lead-form
363 ms
d4889fc5c33d.css
296 ms
26def07bc856.js
320 ms
jquery-1.8.1.min.js
294 ms
jsonlogging.js
264 ms
youtube.js
328 ms
fullscreen.js
323 ms
conversion.js
438 ms
fontawesome-webfont.woff
142 ms
icons.svg
140 ms
status
128 ms
__utm.gif
57 ms
__utm.gif
52 ms
t.dhj
201 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
53 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
77 ms
layout-js-flash-860bd3ac3f031c7decbc0e1c17779e109636da5f.js
487 ms
aIC5imFj_normal.png
343 ms
resim_100_101_normal.jpg
242 ms
o2U0ZZz1_normal.png
334 ms
x8gB9h_N_normal.jpeg
334 ms
292be66e1ca913684c94f304be60d7f2_normal.jpeg
333 ms
ZhWfTENW_normal.jpeg
340 ms
CO7EuvfVEAABhXl.png:small
382 ms
COJ4j3sWgAA5yGO.png:small
478 ms
B-RgrO2CQAA-uzy.png:small
474 ms
B9wmDRvCIAEwmjr.jpg:small
456 ms
BylzcqKIcAApEFU.png:small
2294 ms
ByEadTEIAAA7j7u.png:small
2294 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
376 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
2285 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
90 ms
ad_status.js
2359 ms
cm
264 ms
x35248
2530 ms
DS_CassandraSummit13_300x250.jpg
299 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
2400 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
2409 ms
hbpix
2229 ms
s-3271.xgi
2188 ms
2179 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
281 ms
buttons.ab966a004186897711de4a5ed256c924.css
271 ms
iframe_api
331 ms
326 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
117 ms
316 ms
rum-track
304 ms
91 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
81 ms
st.1188278743c14064d5e8ae56c8ada29c.js
182 ms
213 ms
iframe_api
200 ms
117 ms
112 ms
19505
107 ms
xrefid.xgi
92 ms
118 ms
107 ms
116 ms
125 ms
iframe_api
170 ms
29 ms
www-widgetapi.js
18 ms
102 ms
74 ms
gora.apache.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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
gora.apache.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
gora.apache.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gora.apache.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gora.apache.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.
gora.apache.org
Open Graph description is not detected on the main page of Gora Apache. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: