6.2 sec in total
1.4 sec
4.6 sec
228 ms
Click here to check amazing Greeby content. Otherwise, check out these important facts you probably never knew about greeby.com
Greeby provides on-demand and local Tenant Coordination and Project Management for retail, multi-family, office, and industrial real estate developers
Visit greeby.comWe analyzed Greeby.com page load time and found that the first response time was 1.4 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
greeby.com performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value15.8 s
0/100
25%
Value17.0 s
0/100
10%
Value2,910 ms
3/100
30%
Value1.012
2/100
15%
Value22.0 s
1/100
10%
1364 ms
117 ms
114 ms
220 ms
145 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 64% of them (41 requests) were addressed to the original Greeby.com, 19% (12 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Greeby.com.
Page size can be reduced by 1.7 MB (45%)
3.8 MB
2.1 MB
In fact, the total size of Greeby.com 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. 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.7 MB which makes up the majority of the site volume.
Potential reduce by 99.4 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 99.4 kB or 72% of the original size.
Potential reduce by 108.7 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. Greeby images are well optimized though.
Potential reduce by 431.1 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 431.1 kB or 57% of the original size.
Potential reduce by 1.1 MB
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. Greeby.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 85% of the original size.
Number of requests can be reduced by 30 (60%)
50
20
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greeby. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.greeby.com
1364 ms
style.min.css
117 ms
style.min.css
114 ms
style.min.css
220 ms
style.min.css
145 ms
style.min.css
149 ms
style.min.css
208 ms
ftg.css
166 ms
font-awesome.css
33 ms
style-static.min.css
423 ms
front.js
187 ms
et-core-unified-22.min.css
209 ms
et-core-unified-deferred-22.min.css
213 ms
mediaelementplayer-legacy.min.css
224 ms
wp-mediaelement.min.css
241 ms
map-style.css
247 ms
jquery.min.js
252 ms
jquery-migrate.min.js
225 ms
jquery.finalTilesGallery.js
298 ms
scripts.min.js
475 ms
common.js
286 ms
mediaelement-and-player.min.js
475 ms
mediaelement-migrate.min.js
295 ms
wp-mediaelement.min.js
342 ms
map-interact.js
352 ms
jquery.mobile.js
359 ms
Greeby-Logo-Blue-No-Tag-PNG.png
84 ms
preloader.gif
111 ms
Greeby-Logo-white-No-Tag-PNG-Blue-Offset.png
112 ms
DM200x200Blue191f45.png
63 ms
PM200x200Blue191f45.png
80 ms
TC200x200Blue191f45.png
111 ms
Website-Project-Banner-3.png
187 ms
Greeby-Logo-white-No-Tag-PNG.png
144 ms
Westfield_Southcenter600x450.jpg
183 ms
MB360.jpg
271 ms
Ponce-City-Market-600x400-1.jpg
247 ms
avalonnorthbergen.jpg
188 ms
GreebyTC-logo-297x62-1.png
231 ms
CRRPCDPCRX.png
246 ms
M4xTzrn_50Q
154 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
74 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
97 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
110 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
111 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
111 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
111 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
112 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
110 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
112 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
113 ms
modules.woff
235 ms
www-player.css
62 ms
www-embed-player.js
97 ms
base.js
120 ms
ad_status.js
127 ms
SdShMpdhHIYiz4OAK3X60VwAo5runEsW3RCnPxmRbSs.js
101 ms
embed.js
38 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
10 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
10 ms
id
19 ms
Create
79 ms
GenerateIT
15 ms
style.min.css
67 ms
greeby.com 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
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.
greeby.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
greeby.com 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 Greeby.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 Greeby.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.
greeby.com
Open Graph data is detected on the main page of Greeby. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: