3.3 sec in total
57 ms
1.9 sec
1.4 sec
Click here to check amazing Greaky content. Otherwise, check out these important facts you probably never knew about greaky.com
Android, greaky, jellybean, ICS, kitkat
Visit greaky.comWe analyzed Greaky.com page load time and found that the first response time was 57 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
greaky.com performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value2.6 s
88/100
25%
Value4.1 s
78/100
10%
Value800 ms
36/100
30%
Value0.233
53/100
15%
Value8.0 s
42/100
10%
57 ms
433 ms
30 ms
54 ms
25 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Greaky.com, 40% (49 requests) were made to Apis.google.com and 10% (12 requests) were made to 2.bp.blogspot.com. The less responsive or slowest element that took the longest time to load (873 ms) relates to the external source Apis.google.com.
Page size can be reduced by 365.4 kB (25%)
1.5 MB
1.1 MB
In fact, the total size of Greaky.com main page is 1.5 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 257.7 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 257.7 kB or 86% of the original size.
Potential reduce by 60.9 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. Greaky images are well optimized though.
Potential reduce by 6.2 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 6.2 kB or 13% of the original size.
Potential reduce by 40.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. Greaky.com needs all CSS files to be minified and compressed as it can save up to 40.5 kB or 74% of the original size.
Number of requests can be reduced by 41 (37%)
112
71
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greaky. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
greaky.com
57 ms
www.greaky.com
433 ms
webfont.js
30 ms
3375562265-css_bundle_v2.css
54 ms
gsearch.css
25 ms
authorization.css
101 ms
plusone.js
80 ms
3226477086-widgets.js
84 ms
jsapi
27 ms
css
37 ms
cb=gapi.loaded_0
214 ms
cb=gapi.loaded_1
214 ms
google_top_exp.js
211 ms
icon18_edit_allbkg.gif
210 ms
ChDsHg
211 ms
Download_Mode.JPG
193 ms
Drivers.PNG
193 ms
LiveWallpapers3.png
190 ms
LeftPane.png
191 ms
paging_dot.png
171 ms
icon18_wrench_allbkg.png
171 ms
photo.jpg
164 ms
gprofile_button-16.png
161 ms
cb=gapi.loaded_2
103 ms
cb=gapi.loaded_3
102 ms
fastbutton
178 ms
fastbutton
175 ms
fastbutton
291 ms
fastbutton
287 ms
fastbutton
287 ms
fastbutton
283 ms
fastbutton
326 ms
fastbutton
325 ms
fastbutton
373 ms
fastbutton
417 ms
fastbutton
416 ms
fastbutton
368 ms
fastbutton
413 ms
fastbutton
412 ms
follow
457 ms
159 ms
stats
155 ms
Odin.jpg
159 ms
About.png
248 ms
Applications.png
292 ms
Clock2.png
246 ms
Market.png
288 ms
Maps_4.png
246 ms
Music_Player.png
247 ms
MyFiles.png
340 ms
Alarm.png
339 ms
42.gif
338 ms
Download_Mode.JPG
340 ms
arrow_dropdown.gif
292 ms
share_buttons_20_3.png
148 ms
s_top.png
148 ms
s_bottom.png
190 ms
icon_feed12.png
292 ms
subscribe-netvibes.png
338 ms
subscribe-yahoo.png
384 ms
Clock.png
148 ms
Settings.png
243 ms
Camera.png
141 ms
12.gif
207 ms
3.gif
335 ms
52.gif
337 ms
clear.gif
139 ms
Home.png
149 ms
LiveWallpapers.png
243 ms
Sync.png
384 ms
android-logo-white.png
206 ms
22.gif
335 ms
android-logo-white.png
243 ms
CdSZfRtHbQrBohqmzSdDYKx4dljS8LgdW1vxXN8xI8w.ttf
153 ms
font
242 ms
BjAYBlHtW3CJxDcjzrnZCJ0EAVxt0G0biEntp43Qt6E.ttf
286 ms
commentcount
506 ms
cb=gapi.loaded_4
370 ms
commentcount
507 ms
commentcount
549 ms
commentcount
441 ms
commentcount
452 ms
commentcount
520 ms
commentcount
873 ms
commentcount
572 ms
commentcount
602 ms
commentcount
615 ms
commentcount
653 ms
commentcount
708 ms
commentcount
716 ms
commentcount
871 ms
Moto-360_Map-820x420.jpg
293 ms
blank.html
95 ms
navbar.g
164 ms
cb=gapi.loaded_5
573 ms
postmessageRelay
196 ms
rs=AGLTcCMZnOZwP_q6pCwQUYCN0BCxu9nBPg
550 ms
chart
146 ms
default+en.css
5 ms
default+en.I.js
44 ms
platform:gapi.iframes.style.common.js
536 ms
icons_peach.png
158 ms
arrows-light.png
158 ms
async-ads.js
158 ms
small-logo.png
59 ms
3193398744-postmessagerelay.js
139 ms
rpc:shindig_random.js
462 ms
rs=AGLTcCP9VNIm86MVTpSHyPEpDZAxaY9E9g
317 ms
rs=AGLTcCOFe0ICGMfEiURrBMnTsZI9m_OXug
325 ms
rs=AGLTcCNwaNtIpe7ob3h-eAZtP40g9-0xOw
391 ms
rs=AGLTcCOFe0ICGMfEiURrBMnTsZI9m_OXug
292 ms
cb=gapi.loaded_0
126 ms
cb=gapi.loaded_1
128 ms
cb=gapi.loaded_0
152 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
235 ms
cb=gapi.loaded_0
31 ms
cb=gapi.loaded_1
164 ms
fastbutton
160 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
129 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
128 ms
postmessageRelay
51 ms
greaky.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
greaky.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
greaky.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greaky.com 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 Greaky.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.
greaky.com
Open Graph description is not detected on the main page of Greaky. 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: