2.1 sec in total
134 ms
1.5 sec
429 ms
Click here to check amazing Public Gardens content for United States. Otherwise, check out these important facts you probably never knew about publicgardens.org
Visit publicgardens.orgWe analyzed Publicgardens.org page load time and found that the first response time was 134 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
publicgardens.org performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value6.7 s
7/100
25%
Value4.5 s
72/100
10%
Value570 ms
52/100
30%
Value0.003
100/100
15%
Value9.3 s
31/100
10%
134 ms
63 ms
48 ms
78 ms
61 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 85% of them (62 requests) were addressed to the original Publicgardens.org, 3% (2 requests) were made to Maxcdn.bootstrapcdn.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Publicgardens.org.
Page size can be reduced by 595.4 kB (21%)
2.8 MB
2.2 MB
In fact, the total size of Publicgardens.org main page is 2.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. 45% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 50.5 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 50.5 kB or 78% of the original size.
Potential reduce by 41.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. Public Gardens images are well optimized though.
Potential reduce by 350.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 350.2 kB or 76% of the original size.
Potential reduce by 153.4 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. Publicgardens.org needs all CSS files to be minified and compressed as it can save up to 153.4 kB or 81% of the original size.
Number of requests can be reduced by 52 (73%)
71
19
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Public Gardens. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
publicgardens.org
134 ms
MyFontsWebfontsKit.css
63 ms
font-awesome.min.css
48 ms
css
78 ms
system.base.css
61 ms
system.menus.css
55 ms
system.messages.css
57 ms
system.theme.css
72 ms
views_slideshow.css
61 ms
aet_insert.css
67 ms
date.css
71 ms
datepicker.1.7.css
72 ms
field.css
74 ms
node.css
75 ms
search.css
81 ms
uc_order.css
83 ms
uc_product.css
84 ms
uc_store.css
84 ms
user.css
85 ms
colorbox_style.css
86 ms
ctools.css
92 ms
views_slideshow_controls_text.css
95 ms
views_slideshow_cycle.css
95 ms
nice_menus.css
97 ms
nice_menus_default.css
97 ms
jquery.sidr.dark.css
98 ms
field_group.css
105 ms
field_collection.theme.css
107 ms
gmap.css
107 ms
layout.css
154 ms
style.css
108 ms
colors.css
108 ms
pages.css
115 ms
blocks.css
118 ms
menus.css
118 ms
views.css
134 ms
nodes.css
137 ms
entities.css
128 ms
js
68 ms
fields.css
112 ms
text.css
96 ms
print.css
105 ms
2f5ac8
11 ms
js_JLxuxbhhrFRy-sBnijHkR0TGGHgiukMPv94zvDWgQ3g.js
150 ms
js_wJ4YjN2XpIqgmHVAbXUxoljO_Pr91oWHjEuqdfmr9Bs.js
123 ms
js_b44iQEXWMVV0f52jb408VopXkYqEV1DWKlUvgfA5tyM.js
121 ms
js_BA5XIbSw1Jue_NutKrjWznz0sUSqb2IVaCIdSOpVRok.js
131 ms
js_qJlpB6R78h0jp0r02sCB1XD6HfbtTi0KGnSQgvhC05E.js
112 ms
js_Q1Xea2OOZYp_nM0eT9zsaKTiehszwsiRPMSRj2JhO2s.js
111 ms
gmap_markers.js
110 ms
js_U_r4Ow684AgBgpxadQenSqvXEteOYjU3Wsx5yPcJih8.js
117 ms
js_xJZnsuF-ggeL6Dl_BtBr-wnnG_c0A9nsGlrPQFnb6wA.js
121 ms
analytics.js
66 ms
logo.svg
123 ms
icon-apgaicon-sprite.png
39 ms
arrow-right.png
38 ms
Annual-Appeal-Background.png
1129 ms
2016-apga-miami-min.jpg
812 ms
2016-education-symposium-min.jpg
481 ms
publicgardens.org
345 ms
icon-apga.png
89 ms
Cover_Public_Garden_Mag_.png
391 ms
map-home-bg.jpg
236 ms
3430.png
392 ms
2F5AC8_3_0.woff
392 ms
fontawesome-webfont.woff
41 ms
ados.js
41 ms
collect
33 ms
bg-floral.jpg
425 ms
icon-search.png
320 ms
ados
90 ms
9495d5dbb306485baf78078c769ce3fa.jpg
5 ms
i.gif
20 ms
publicgardens.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
Image elements do not have [alt] attributes
Links do not have a discernible name
publicgardens.org 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
publicgardens.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Publicgardens.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 Publicgardens.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.
publicgardens.org
Open Graph description is not detected on the main page of Public Gardens. 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: