Tools & Wizards About Us
iloveponds.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

iloveponds.com

Aquatic Landscaping in New England | Ponds & Water Features Specialist

Page Load Speed

4.1 sec in total

First Response

411 ms

Resources Loaded

2.7 sec

Page Rendered

1 sec

iloveponds.com screenshot

About Website

Click here to check amazing Ilove Ponds content. Otherwise, check out these important facts you probably never knew about iloveponds.com

Make your outdoor living space come alive with the sights and sounds of water. At New England Aquatic Landscaping, we use the power of water to add sound and movement to your yard, and to take your la...

Visit iloveponds.com

Key Findings

We analyzed Iloveponds.com page load time and found that the first response time was 411 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

iloveponds.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value3,020 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.225

55/100

15%

TTI (Time to Interactive)

Value26.1 s

0/100

10%

Network Requests Diagram

iloveponds.com

411 ms

animations.css

130 ms

style.css

195 ms

text-editor.css

195 ms

style.min.css

206 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 87% of them (83 requests) were addressed to the original Iloveponds.com, 6% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Dashboard.searchatlas.com. The less responsive or slowest element that took the longest time to load (704 ms) belongs to the original domain Iloveponds.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.6 kB (10%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images

In fact, the total size of Iloveponds.com main page is 2.1 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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 157.2 kB

  • Original 182.8 kB
  • After minification 176.4 kB
  • After compression 25.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 157.2 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 61.4 kB

  • Original 2.0 MB
  • After minification 1.9 MB

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. Ilove Ponds images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 58 (70%)

Requests Now

83

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ilove Ponds. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

iloveponds.com

iloveponds.com

411 ms

animations.css

animations.css

130 ms

style.css

style.css

195 ms

text-editor.css

text-editor.css

195 ms

style.min.css

style.min.css

206 ms

theme.min.css

theme.min.css

198 ms

header-footer.min.css

header-footer.min.css

197 ms

frontend.min.css

frontend.min.css

202 ms

widget-image.min.css

widget-image.min.css

261 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

262 ms

widget-heading.min.css

widget-heading.min.css

264 ms

widget-icon-list.min.css

widget-icon-list.min.css

265 ms

widget-divider.min.css

widget-divider.min.css

269 ms

widget-text-editor.min.css

widget-text-editor.min.css

270 ms

widget-social-icons.min.css

widget-social-icons.min.css

327 ms

apple-webkit.min.css

apple-webkit.min.css

330 ms

elementor-icons.min.css

elementor-icons.min.css

329 ms

css

css

32 ms

swiper.min.css

swiper.min.css

331 ms

e-swiper.min.css

e-swiper.min.css

336 ms

post-9.css

post-9.css

336 ms

dashicons.min.css

dashicons.min.css

457 ms

frontend.min.css

frontend.min.css

395 ms

widget-menu-anchor.min.css

widget-menu-anchor.min.css

393 ms

widget-video.min.css

widget-video.min.css

399 ms

widget-gallery.min.css

widget-gallery.min.css

402 ms

e-gallery.min.css

e-gallery.min.css

401 ms

widget-star-rating.min.css

widget-star-rating.min.css

465 ms

post-54.css

post-54.css

461 ms

all.min.css

all.min.css

470 ms

v4-shims.min.css

v4-shims.min.css

468 ms

post-11.css

post-11.css

473 ms

post-15.css

post-15.css

520 ms

front-widget.css

front-widget.css

526 ms

fontawesome.min.css

fontawesome.min.css

528 ms

solid.min.css

solid.min.css

535 ms

brands.min.css

brands.min.css

535 ms

js

js

61 ms

javascript;base64,dmFyIHNjcmlwdCA9IGRvY3VtZW50LmNyZWF0ZUVsZW1lbnQoInNjcmlwdCIpO3NjcmlwdC5zcmMgPSAnaHR0cHM6Ly9kYXNoYm9hcmQuc2VhcmNoYXRsYXMuY29tL3NjcmlwdHMvb3R0by5qcyc7ZG9jdW1lbnQuaGVhZC5hcHBlbmRDaGlsZChzY3JpcHQpOw==

javascript;base64,dmFyIHNjcmlwdCA9IGRvY3VtZW50LmNyZWF0ZUVsZW1lbnQoInNjcmlwdCIpO3NjcmlwdC5zcmMgPSAnaHR0cHM6Ly9kYXNoYm9hcmQuc2VhcmNoYXRsYXMuY29tL3NjcmlwdHMvb3R0by5qcyc7ZG9jdW1lbnQuaGVhZC5hcHBlbmRDaGlsZChzY3JpcHQpOw==

1 ms

style.min.css

style.min.css

479 ms

dynamic-visibility.min.css

dynamic-visibility.min.css

463 ms

platform.js

platform.js

475 ms

jquery.min.js

jquery.min.js

479 ms

jquery-migrate.min.js

jquery-migrate.min.js

411 ms

v4-shims.min.js

v4-shims.min.js

412 ms

sdk.min.js

sdk.min.js

410 ms

cute-alert.js

cute-alert.js

447 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

446 ms

jquery.sticky.min.js

jquery.sticky.min.js

446 ms

e-gallery.min.js

e-gallery.min.js

557 ms

front-widget.js

front-widget.js

553 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

552 ms

webpack.runtime.min.js

webpack.runtime.min.js

495 ms

frontend-modules.min.js

frontend-modules.min.js

511 ms

hooks.min.js

hooks.min.js

493 ms

i18n.min.js

i18n.min.js

508 ms

frontend.min.js

frontend.min.js

503 ms

core.min.js

core.min.js

503 ms

frontend.min.js

frontend.min.js

512 ms

elements-handlers.min.js

elements-handlers.min.js

444 ms

otto.js

otto.js

155 ms

banner.jpg

banner.jpg

315 ms

logo-neal.png

logo-neal.png

289 ms

i-love-ponds-logo.png

i-love-ponds-logo.png

286 ms

pond-maintenance.jpg

pond-maintenance.jpg

270 ms

pond-repair.jpg

pond-repair.jpg

287 ms

pond-construction.jpg

pond-construction.jpg

287 ms

service-4-fountainscape.jpg

service-4-fountainscape.jpg

328 ms

service-5-pondless.jpg

service-5-pondless.jpg

406 ms

service-6-swimming-ponds.jpg

service-6-swimming-ponds.jpg

363 ms

fountainscapes-26.jpg

fountainscapes-26.jpg

547 ms

pond-55.jpg

pond-55.jpg

548 ms

team-image.jpg

team-image.jpg

419 ms

call-1.png

call-1.png

395 ms

work-1.png

work-1.png

431 ms

enjoy-1.png

enjoy-1.png

462 ms

this-old-house.jpg

this-old-house.jpg

481 ms

pond-stars.jpg

pond-stars.jpg

488 ms

aquascape-logo.jpg

aquascape-logo.jpg

504 ms

best-houzz-1.jpg

best-houzz-1.jpg

590 ms

cac-logo.png

cac-logo.png

552 ms

header-neal-home.jpg

header-neal-home.jpg

601 ms

pond-52.jpg

pond-52.jpg

704 ms

footer-image-scaled.jpg

footer-image-scaled.jpg

637 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

121 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

133 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

134 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

133 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

133 ms

fa-brands-400.woff

fa-brands-400.woff

535 ms

eicons.woff

eicons.woff

547 ms

fa-solid-900.woff

fa-solid-900.woff

581 ms

fa-regular-400.woff

fa-regular-400.woff

547 ms

dynamic_optimization.js

dynamic_optimization.js

46 ms

Accessibility Review

iloveponds.com accessibility score

98

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

iloveponds.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

iloveponds.com SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iloveponds.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 Iloveponds.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.

Social Sharing Optimization

iloveponds.com

Open Graph data is detected on the main page of Ilove Ponds. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: