5 sec in total
1 sec
2.8 sec
1.2 sec
Visit greengrass.com now to see the best up-to-date Greengrass content and also check out these interesting facts you probably never knew about greengrass.com
Since 1986, Fore Better Golf offers premium services in golf printing & design. Trusted by global golf facilities for unmatched value. Explore now!
Visit greengrass.comWe analyzed Greengrass.com page load time and found that the first response time was 1 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
greengrass.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value20.8 s
0/100
25%
Value7.4 s
28/100
10%
Value240 ms
85/100
30%
Value0.131
81/100
15%
Value12.1 s
16/100
10%
1048 ms
169 ms
111 ms
190 ms
25 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Greengrass.com, 5% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Forebettergolf.com.
Page size can be reduced by 1.7 MB (18%)
9.4 MB
7.7 MB
In fact, the total size of Greengrass.com main page is 9.4 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. 70% of websites need less resources to load. Images take 7.6 MB which makes up the majority of the site volume.
Potential reduce by 168.8 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 168.8 kB or 86% of the original size.
Potential reduce by 268.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. Greengrass images are well optimized though.
Potential reduce by 762.0 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 762.0 kB or 71% of the original size.
Potential reduce by 515.2 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. Greengrass.com needs all CSS files to be minified and compressed as it can save up to 515.2 kB or 88% of the original size.
Number of requests can be reduced by 23 (46%)
50
27
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greengrass. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
forebettergolf.com
1048 ms
twemoji.js
169 ms
wp-emoji.js
111 ms
layerslider.css
190 ms
css
25 ms
bbpress.css
191 ms
styles.css
144 ms
settings.css
215 ms
css
33 ms
style.css
794 ms
font-awesome.css
225 ms
ilightbox.css
437 ms
animations.css
311 ms
bbpress.css
266 ms
greensock.js
339 ms
jquery.js
478 ms
jquery-migrate.js
373 ms
layerslider.kreaturamedia.jquery.js
445 ms
layerslider.transitions.js
413 ms
jquery.themepunch.tools.min.js
623 ms
jquery.themepunch.revolution.min.js
476 ms
editor.js
173 ms
jquery.form.min.js
175 ms
scripts.js
217 ms
comment-reply.js
207 ms
main.min.js
708 ms
Logo_small1.png
68 ms
Logo2.png
88 ms
home_screen_bkg1-1024x512.png
399 ms
FBG_Cover.png
947 ms
home_screen_bkg-1024x517.png
489 ms
scorecards.png
401 ms
smartphone_apps.png
396 ms
pin_sheets.png
655 ms
sprinkler_tags.png
397 ms
yardage_books.png
400 ms
yardage_cards.png
502 ms
outing_book.png
581 ms
combo_book.png
457 ms
glass_awards.png
526 ms
bag_tag1.png
541 ms
calendars.png
610 ms
yardage_cartbook.png
599 ms
placemats.png
756 ms
menu_cards.png
834 ms
rack_cards.png
660 ms
photography.png
719 ms
website_graphics.png
871 ms
signage_markers.png
728 ms
golf_maps.png
830 ms
seasonal_cards.png
793 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
7 ms
0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf
26 ms
8c9q46CAcsp9TiRX9KLgZC3USBnSvpkopQaUR-2r7iU.ttf
26 ms
icomoon.woff
783 ms
greengrass.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
greengrass.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
greengrass.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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greengrass.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 Greengrass.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.
greengrass.com
Open Graph data is detected on the main page of Greengrass. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: