4.7 sec in total
1.2 sec
3.1 sec
403 ms
Visit divacup.com now to see the best up-to-date DIVA Cup content for United States and also check out these interesting facts you probably never knew about divacup.com
As makers of the Original DIVA™ Cup and the most trusted name in the period care category, we innovate with the same integrity we started with over 20 years ago. Our conscious approach instills confid...
Visit divacup.comWe analyzed Divacup.com page load time and found that the first response time was 1.2 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
divacup.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value6.9 s
6/100
25%
Value3.4 s
90/100
10%
Value540 ms
54/100
30%
Value0
100/100
15%
Value7.0 s
53/100
10%
1222 ms
596 ms
207 ms
315 ms
57 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 26% of them (30 requests) were addressed to the original Divacup.com, 25% (29 requests) were made to Maps.google.com and 8% (9 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Divacup.com.
Page size can be reduced by 1.1 MB (34%)
3.2 MB
2.1 MB
In fact, the total size of Divacup.com main page is 3.2 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.7 MB which makes up the majority of the site volume.
Potential reduce by 87.2 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 87.2 kB or 75% of the original size.
Potential reduce by 69.0 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. DIVA Cup images are well optimized though.
Potential reduce by 719.9 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 719.9 kB or 64% of the original size.
Potential reduce by 227.7 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. Divacup.com needs all CSS files to be minified and compressed as it can save up to 227.7 kB or 82% of the original size.
Number of requests can be reduced by 47 (45%)
105
58
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DIVA Cup. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
divacup.com
1222 ms
minify.php
596 ms
minify.php
207 ms
minify.php
315 ms
language-selector.css
57 ms
font-awesome.min.css
26 ms
minify.php
730 ms
minify.php
817 ms
minify.php
934 ms
css
27 ms
minify.php
993 ms
js
54 ms
minify.php
1100 ms
minify.php
1221 ms
conversion.js
14 ms
addthis_widget.js
13 ms
wp-emoji-release.min.js
155 ms
analytics.js
21 ms
collect
54 ms
collect
61 ms
Swirl_Header7.fw_-.png
129 ms
logo.png
99 ms
Pink_Earth.fw_1.png
55 ms
White-Home-Button2.fw_.png
78 ms
Facebook_40.fw_.png
128 ms
Twitter_40.fw_.png
128 ms
Youtube_40.fw_.png
129 ms
Instagram-40.png
132 ms
Pinterest.fw_.png
133 ms
google-plus-40.png
136 ms
bg-slider.png
204 ms
harris-teeter.jpg
254 ms
DivaWash-Slider-EN-1600x400-e1443011021855.jpg
186 ms
Diva-Product-Slider2.jpg
252 ms
OMG-large-banner1.jpg
304 ms
search_button.png
253 ms
yxRIRo8z0po
118 ms
5NLAltYsmEI
161 ms
ejLRhBEorqjLDaF8s-xuTQ.ttf
56 ms
koFYE26bhT88HgRA8f4vbS3USBnSvpkopQaUR-2r7iU.ttf
78 ms
widgets.js
22 ms
geRI9Tt6_9xDj8YKwTdHyA.ttf
41 ms
fontawesome-webfont.woff
25 ms
www-embed-player-vflZsBgOl.css
57 ms
www-embed-player.js
77 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
29 ms
ad_status.js
27 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
57 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
67 ms
93 ms
common.js
60 ms
util.js
74 ms
geocoder.js
73 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
69 ms
1236.js
28 ms
51 ms
bullets.png
52 ms
syndication
121 ms
349625721653710848
248 ms
AuthenticationService.Authenticate
44 ms
GeocodeService.Search
59 ms
s
40 ms
infowindow.js
24 ms
u
62 ms
map.js
10 ms
admin-ajax.php
298 ms
onion.js
16 ms
openhand_8_8.cur
29 ms
ViewportInfoService.GetViewportInfo
93 ms
stats.js
14 ms
controls.js
15 ms
transparent.png
22 ms
css
41 ms
google4.png
35 ms
marker.js
28 ms
mapcnt6.png
38 ms
sv5.png
39 ms
tmapctrl.png
40 ms
cb_scout5.png
45 ms
tmapctrl4.png
45 ms
imgs8.png
44 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
35 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
34 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
35 ms
vt
26 ms
vt
40 ms
vt
30 ms
vt
34 ms
vt
33 ms
vt
35 ms
vt
35 ms
vt
38 ms
vt
36 ms
vt
35 ms
vt
38 ms
vt
38 ms
vt
45 ms
vt
44 ms
vt
45 ms
vt
46 ms
vt
47 ms
vt
47 ms
vt
47 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
22 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
18 ms
gkxE-lOf_normal.jpg
162 ms
7bZO99UO_normal.png
158 ms
CcZjJFQWAAAHE5j.jpg:small
159 ms
CcKGY5uWAAAG9g_.jpg:small
162 ms
CcApBNwXIAAy-1r.png:small
169 ms
Cb1gBI_W8AI6AYZ.jpg:small
162 ms
CbmDQMZVIAA8agA.png:small
164 ms
CbdZVD5W8AAKh1N.jpg:small
158 ms
CbR4Wq7W4AQm2Vi.jpg:small
162 ms
300lo.json
114 ms
sh.7c7179124ea24ac6ba46caac.html
68 ms
divacup.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
divacup.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
divacup.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Divacup.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 Divacup.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.
divacup.com
Open Graph data is detected on the main page of DIVA Cup. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: