5.8 sec in total
1.2 sec
4.2 sec
433 ms
Click here to check amazing What Pond content for United States. Otherwise, check out these important facts you probably never knew about whatpond.com
WhatPond, Your Pond Specialist, from Pond Building to Pond Management Solutions.
Visit whatpond.comWe analyzed Whatpond.com page load time and found that the first response time was 1.2 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
whatpond.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value7.0 s
6/100
25%
Value4.0 s
81/100
10%
Value280 ms
80/100
30%
Value0.229
54/100
15%
Value8.2 s
40/100
10%
1229 ms
133 ms
132 ms
131 ms
153 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 60% of them (74 requests) were addressed to the original Whatpond.com, 7% (8 requests) were made to Apis.google.com and 5% (6 requests) were made to Forms.aweber.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Whatpond.com.
Page size can be reduced by 1.1 MB (56%)
2.0 MB
867.8 kB
In fact, the total size of Whatpond.com main page is 2.0 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. Javascripts take 911.1 kB which makes up the majority of the site volume.
Potential reduce by 128.6 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 128.6 kB or 80% of the original size.
Potential reduce by 8.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. What Pond images are well optimized though.
Potential reduce by 635.7 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 635.7 kB or 70% of the original size.
Potential reduce by 351.3 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. Whatpond.com needs all CSS files to be minified and compressed as it can save up to 351.3 kB or 78% of the original size.
Number of requests can be reduced by 88 (75%)
118
30
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Pond. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
www.whatpond.com
1229 ms
css.css
133 ms
eMember_style.css
132 ms
eMember_custom_style.css
131 ms
validationEngine.jquery.css
153 ms
jquery.fileuploader.css
129 ms
dashicons.min.css
207 ms
thickbox.css
195 ms
wp-customer-reviews-generated.css
197 ms
colorbox.css
196 ms
minimalist.css
10 ms
jquery.fancybox.css
200 ms
jquery.fancybox-buttons.css
201 ms
jquery.fancybox-thumbs.css
268 ms
wp_lightbox_ultimate.css
266 ms
wp_lightbox_ultimate_custom.css
265 ms
user.css
270 ms
default.css
269 ms
jquery.js
334 ms
jquery-migrate.min.js
331 ms
jquery.external.lib.js
329 ms
jquery.lightbox-0.5.pack.js
332 ms
jquery.fileuploader.js
332 ms
jquery.validationEngine.js
355 ms
jquery.hint.js
396 ms
jquery.tools18.min.js
460 ms
jquery.libs.js
397 ms
jquery.pagination-2.0rc.js
398 ms
jquery.confirm-1.3.js
399 ms
tooltips.js
400 ms
wp-customer-reviews.js
467 ms
colorbox.js
467 ms
flowplayer.min.js
5 ms
jquery.mousewheel-3.0.6.pack.js
474 ms
jquery.fancybox.pack.js
475 ms
jquery.fancybox-buttons.js
478 ms
jquery.fancybox-media.js
523 ms
jquery.fancybox-thumbs.js
524 ms
jquery.textfill.min.js
52 ms
in.js
9 ms
brand
14 ms
brand
23 ms
sitelock.js
32 ms
pinit.js
8 ms
eStore_extra_shortcode_css.css
475 ms
affiliate_platform_style.css
407 ms
wp_eStore_style.css
409 ms
wp_eStore_custom_style.css
410 ms
wp_pg_style.css
458 ms
html5lightbox.js
455 ms
view.js
414 ms
eStore_read_form.js
410 ms
thickbox.js
427 ms
core.min.js
435 ms
widget.min.js
510 ms
mouse.min.js
506 ms
sortable.min.js
444 ms
hoverIntent.js
443 ms
superfish.min.js
441 ms
jquery.meanmenu.js
441 ms
jquery.orbit-1.3.0.min.js
511 ms
wp-embed.min.js
451 ms
wp-emoji-release.min.js
450 ms
secureAnonymousFramework
120 ms
PinExt.png
22 ms
displays.htm
99 ms
whatpond.com
97 ms
a-few-hours-later.jpg
729 ms
whatpond-logo-address-email.png
444 ms
wanda-boys-wheeeler-300x169.jpg
398 ms
Aeration-125.jpg
441 ms
pond-supplies-125.jpg
443 ms
pond-education-125.jpg
441 ms
join-125.jpg
440 ms
youtube.png
523 ms
twitter.png
522 ms
facebook.png
521 ms
linkedin.png
522 ms
rss.png
520 ms
displays.htm
94 ms
analytics.js
32 ms
google_custom_search_watermark.gif
144 ms
fdd
82 ms
15d.png
80 ms
collect
37 ms
a03
38 ms
07c.png
35 ms
like.php
344 ms
share
337 ms
sprite_connect_v14.png
350 ms
xByw9rDpHns
314 ms
ga.js
228 ms
plusone.js
271 ms
css
276 ms
overlay.png
371 ms
next.png
370 ms
prev.png
369 ms
close.png
370 ms
loadingAnimation.gif
370 ms
border.png
466 ms
controls.png
454 ms
pinit_main.js
78 ms
__utm.gif
48 ms
qeKvIRsJabD.js
533 ms
LVx-xkvaJ0b.png
529 ms
cb=gapi.loaded_0
70 ms
cb=gapi.loaded_1
90 ms
fastbutton
155 ms
www-embed-player-vfl8xM8me.css
103 ms
www-embed-player.js
167 ms
base.js
264 ms
count.json
158 ms
postmessageRelay
122 ms
cb=gapi.loaded_0
57 ms
cb=gapi.loaded_1
56 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
97 ms
3193398744-postmessagerelay.js
193 ms
rpc:shindig_random.js
41 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
25 ms
ad_status.js
103 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
20 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
21 ms
cb=gapi.loaded_0
10 ms
whatpond.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.
whatpond.com 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
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
whatpond.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 Whatpond.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 Whatpond.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.
whatpond.com
Open Graph description is not detected on the main page of What Pond. 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: