Tools & Wizards About Us
plungesandiego.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

plungesandiego.com

Open Public Swimming Pool Near Me | Plunge San Diego

Page Load Speed

2.7 sec in total

First Response

70 ms

Resources Loaded

1.1 sec

Page Rendered

1.6 sec

plungesandiego.com screenshot

About Website

Visit plungesandiego.com now to see the best up-to-date Plunge San Diego content and also check out these interesting facts you probably never knew about plungesandiego.com

The iconic open pool in Mission Beach. Cutting-edge fitness equipment and classes. Swim lessons, private swim lessons and party rentals available.

Visit plungesandiego.com

Key Findings

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

Performance Metrics

plungesandiego.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

plungesandiego.com

70 ms

plungesandiego.com

67 ms

gtm.js

69 ms

gtm.js

108 ms

6187.js

31 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 94% of them (119 requests) were addressed to the original Plungesandiego.com, 2% (3 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (286 ms) belongs to the original domain Plungesandiego.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 170.9 kB (13%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Plungesandiego.com main page is 1.3 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.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 159.8 kB

  • Original 191.6 kB
  • After minification 181.0 kB
  • After compression 31.7 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 159.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 79 B

  • Original 1.0 MB
  • After minification 1.0 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. Plunge San Diego images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 11.0 kB

  • Original 90.6 kB
  • After minification 90.4 kB
  • After compression 79.6 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 11.0 kB or 12% of the original size.

CSS Optimization

-0%

Potential reduce by 43 B

  • Original 14.5 kB
  • After minification 14.5 kB
  • After compression 14.5 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. Plungesandiego.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 90 (82%)

Requests Now

110

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

plungesandiego.com

plungesandiego.com

70 ms

plungesandiego.com

plungesandiego.com

67 ms

gtm.js

gtm.js

69 ms

gtm.js

gtm.js

108 ms

6187.js

6187.js

31 ms

ai1ec_parsed_css.css

ai1ec_parsed_css.css

47 ms

dashicons.min.css

dashicons.min.css

42 ms

variables-skeleton.min.css

variables-skeleton.min.css

63 ms

variables-full.min.css

variables-full.min.css

43 ms

common-skeleton.min.css

common-skeleton.min.css

35 ms

common-full.min.css

common-full.min.css

59 ms

tickets.min.css

tickets.min.css

79 ms

rsvp-v1.min.css

rsvp-v1.min.css

81 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

80 ms

style.min.css

style.min.css

84 ms

jquery.datetimepicker.min.css

jquery.datetimepicker.min.css

82 ms

fonts.css

fonts.css

99 ms

all.css

all.css

123 ms

slick.css

slick.css

97 ms

fancybox.css

fancybox.css

96 ms

bootstrap.min.css

bootstrap.min.css

101 ms

light.css

light.css

107 ms

style.css

style.css

118 ms

rsvp.min.css

rsvp.min.css

126 ms

tpp.min.css

tpp.min.css

136 ms

masterslider.main.css

masterslider.main.css

133 ms

custom.css

custom.css

138 ms

style.min.css

style.min.css

135 ms

jquery.min.js

jquery.min.js

135 ms

jquery-migrate.min.js

jquery-migrate.min.js

134 ms

light.js

light.js

181 ms

jquery.min.js

jquery.min.js

160 ms

slick.min.js

slick.min.js

158 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

205 ms

bootstrap.min.js

bootstrap.min.js

159 ms

parallax.min.js

parallax.min.js

157 ms

custom.js

custom.js

161 ms

email-decode.min.js

email-decode.min.js

160 ms

bootstrap-datepicker.standalone.min.css

bootstrap-datepicker.standalone.min.css

264 ms

tooltipster.bundle.min.css

tooltipster.bundle.min.css

286 ms

plungesandiego.com.json

plungesandiego.com.json

75 ms

views-skeleton.min.css

views-skeleton.min.css

261 ms

views-skeleton.min.css

views-skeleton.min.css

253 ms

views-full.min.css

views-full.min.css

250 ms

views-full.min.css

views-full.min.css

251 ms

archives.min.css

archives.min.css

234 ms

ticket-details.min.js

ticket-details.min.js

231 ms

rsvp.min.js

rsvp.min.js

228 ms

jquery.datetimepicker.full.min.js

jquery.datetimepicker.full.min.js

217 ms

datetimepicker.js

datetimepicker.js

212 ms

script.min.js

script.min.js

216 ms

tribe-common.min.js

tribe-common.min.js

213 ms

analytics.js

analytics.js

65 ms

accordion.min.js

accordion.min.js

201 ms

week-day-selector.min.js

week-day-selector.min.js

201 ms

core.min.js

core.min.js

202 ms

mouse.min.js

mouse.min.js

202 ms

draggable.min.js

draggable.min.js

194 ms

jquery.nanoscroller.min.js

jquery.nanoscroller.min.js

184 ms

week-grid-scroller.min.js

week-grid-scroller.min.js

177 ms

week-event-link.min.js

week-event-link.min.js

176 ms

week-multiday-toggle.min.js

week-multiday-toggle.min.js

174 ms

map-events-scroller.min.js

map-events-scroller.min.js

171 ms

toggle-recurrence.min.js

toggle-recurrence.min.js

170 ms

swiper.min.js

swiper.min.js

169 ms

map-no-venue-modal.min.js

map-no-venue-modal.min.js

175 ms

map-provider-google-maps.min.js

map-provider-google-maps.min.js

182 ms

map-events.min.js

map-events.min.js

183 ms

bootstrap-datepicker.min.js

bootstrap-datepicker.min.js

182 ms

datepicker.min.js

datepicker.min.js

180 ms

datepicker-pro.min.js

datepicker-pro.min.js

185 ms

multiday-events.min.js

multiday-events.min.js

181 ms

multiday-events-pro.min.js

multiday-events-pro.min.js

181 ms

collect

collect

129 ms

tooltipster.bundle.min.js

tooltipster.bundle.min.js

166 ms

tooltip.min.js

tooltip.min.js

79 ms

tooltip-pro.min.js

tooltip-pro.min.js

75 ms

query-string.min.js

query-string.min.js

83 ms

underscore-before.js

underscore-before.js

68 ms

underscore.min.js

underscore.min.js

67 ms

underscore-after.js

underscore-after.js

68 ms

manager.min.js

manager.min.js

65 ms

navigation-scroll.min.js

navigation-scroll.min.js

66 ms

month-grid.min.js

month-grid.min.js

83 ms

breakpoints.min.js

breakpoints.min.js

80 ms

viewport.min.js

viewport.min.js

81 ms

month-mobile-events.min.js

month-mobile-events.min.js

107 ms

view-selector.min.js

view-selector.min.js

77 ms

events-bar-inputs.min.js

events-bar-inputs.min.js

78 ms

ical-links.min.js

ical-links.min.js

104 ms

events-bar.min.js

events-bar.min.js

104 ms

lazyload.min.js

lazyload.min.js

102 ms

open-sans-normal-400.woff

open-sans-normal-400.woff

103 ms

open-sans-normal-300.woff

open-sans-normal-300.woff

168 ms

open-sans-normal-600.woff

open-sans-normal-600.woff

102 ms

open-sans-normal-700.woff

open-sans-normal-700.woff

165 ms

open-sans-normal-800.woff

open-sans-normal-800.woff

167 ms

oswald-normal-700.woff

oswald-normal-700.woff

165 ms

oswald-normal-600.woff

oswald-normal-600.woff

165 ms

oswald-normal-500.woff

oswald-normal-500.woff

165 ms

oswald-normal-400.woff

oswald-normal-400.woff

165 ms

js

js

91 ms

oswald-normal-300.woff

oswald-normal-300.woff

162 ms

oswald-normal-200.woff

oswald-normal-200.woff

161 ms

fa-solid-900.woff

fa-solid-900.woff

132 ms

fa-regular-400.woff

fa-regular-400.woff

178 ms

fa-light-300.woff

fa-light-300.woff

174 ms

fa-brands-400.woff

fa-brands-400.woff

173 ms

plunge_logo.png

plunge_logo.png

172 ms

plunge-home-hero.jpg

plunge-home-hero.jpg

173 ms

views-print.min.css

views-print.min.css

69 ms

logo.png

logo.png

39 ms

Egg-Hunt-Banner-2.png

Egg-Hunt-Banner-2.png

58 ms

Sweethearts-Lounge.png

Sweethearts-Lounge.png

50 ms

Events-website-tiles-1.png

Events-website-tiles-1.png

41 ms

Junior-Lifeguards-Banner-First-Edition-1.png

Junior-Lifeguards-Banner-First-Edition-1.png

70 ms

recreatoional-swim-new.jpg

recreatoional-swim-new.jpg

48 ms

premium-day-camps-new.jpg

premium-day-camps-new.jpg

70 ms

swimming_lessons.jpg

swimming_lessons.jpg

78 ms

1.png

1.png

74 ms

AD-SLIDER-FOR-WEBSITE.png

AD-SLIDER-FOR-WEBSITE.png

79 ms

8.png

8.png

84 ms

logo-dark-lg.png

logo-dark-lg.png

105 ms

Drone-Photo.jpg

Drone-Photo.jpg

98 ms

embed

embed

199 ms

views-print.min.css

views-print.min.css

31 ms

js

js

49 ms

Accessibility Review

plungesandiego.com accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes are not valid or misspelled

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

plungesandiego.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

plungesandiego.com SEO score

76

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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 Plungesandiego.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 Plungesandiego.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

plungesandiego.com

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