5.5 sec in total
1.5 sec
3.8 sec
180 ms
Click here to check amazing DEFEND content for United States. Otherwise, check out these important facts you probably never knew about defend.com
Visit defend.comWe analyzed Defend.com page load time and found that the first response time was 1.5 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
defend.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.4 s
9/100
25%
Value4.4 s
74/100
10%
Value230 ms
86/100
30%
Value2.383
0/100
15%
Value7.1 s
52/100
10%
1516 ms
169 ms
383 ms
112 ms
128 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 82% of them (59 requests) were addressed to the original Defend.com, 4% (3 requests) were made to Cdn-gae-default.instantsearchplus.com and 4% (3 requests) were made to Mydentinternational.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Defend.com.
Page size can be reduced by 1.2 MB (48%)
2.4 MB
1.3 MB
In fact, the total size of Defend.com main page is 2.4 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. 40% of websites need less resources to load. Images take 967.1 kB which makes up the majority of the site volume.
Potential reduce by 64.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 64.7 kB or 82% of the original size.
Potential reduce by 56.9 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. DEFEND images are well optimized though.
Potential reduce by 620.4 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 620.4 kB or 69% of the original size.
Potential reduce by 429.0 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. Defend.com needs all CSS files to be minified and compressed as it can save up to 429.0 kB or 86% of the original size.
Number of requests can be reduced by 50 (71%)
70
20
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DEFEND. 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 15 to 1 for CSS and as a result speed up the page load time.
www.defend.com
1516 ms
wp-emoji-release.min.js
169 ms
style.css
383 ms
karma-cool-blue.css
112 ms
secondary-cool-blue.css
128 ms
_font-awesome.css
225 ms
_woocommerce.css
274 ms
_mobile.css
324 ms
wcis_plugin.css
222 ms
render_item1.css
277 ms
settings.css
445 ms
select2.css
327 ms
woocommerce-layout.css
331 ms
woocommerce.css
514 ms
jquery.js
549 ms
jquery-migrate.min.js
396 ms
acp-magento.js
122 ms
core.min.js
434 ms
effect.min.js
491 ms
nbpFrontEnd.js
487 ms
nbpAnimate.js
525 ms
jquery.themepunch.tools.min.js
704 ms
jquery.themepunch.revolution.min.js
763 ms
css
23 ms
css
36 ms
custom-main.js
147 ms
superfish.js
117 ms
jquery.flexslider.js
133 ms
jquery.fitvids.js
116 ms
jquery.isotope.js
171 ms
widget.min.js
157 ms
tabs.min.js
187 ms
accordion.min.js
224 ms
jquery.prettyPhoto.js
317 ms
comment-reply.js
245 ms
add-to-cart.min.js
240 ms
select2.min.js
318 ms
jquery.blockUI.min.js
316 ms
woocommerce.min.js
316 ms
jquery.cookie.min.js
333 ms
cart-fragments.min.js
316 ms
wp-embed.min.js
332 ms
analytics.js
5 ms
collect
32 ms
collect
82 ms
isp.v.2.0.1.min.js
18 ms
overlay-rays.png
79 ms
defend30years-logo.png
286 ms
global-sprite.png
283 ms
bg-div-main.png
285 ms
dummy.png
286 ms
2016-catalog-graphic.jpg
284 ms
samples-box-2.jpg
286 ms
marketplace.jpg
286 ms
new-products-box2.jpg
287 ms
find-dealer.jpg
287 ms
loader-trans.gif
264 ms
arrows.png
263 ms
bg-div-footer-top.png
264 ms
bg-footer-bottom-cool-blue.png
264 ms
fontawesome-webfont.woff
258 ms
www.defend.com
780 ms
post_load
135 ms
load
114 ms
shadow3.png
58 ms
coloredbg.png
56 ms
slider1back.jpg
520 ms
doublearrow2.png
189 ms
slide1defend.png
462 ms
DPS-2011.jpg
206 ms
pop
40 ms
woocommerce-smallscreen.css
57 ms
defend.com accessibility score
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
defend.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
defend.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
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 Defend.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 Defend.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.
defend.com
Open Graph description is not detected on the main page of DEFEND. 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: