10.1 sec in total
715 ms
8.9 sec
462 ms
Welcome to dumblr.com homepage info - get ready to check Dumblr best content right away, or after learning these important things about dumblr.com
Dumb and Dumber To - Own it Digital HD February 3, Blu-ray™ & DVD February 17
Visit dumblr.comWe analyzed Dumblr.com page load time and found that the first response time was 715 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dumblr.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value2.7 s
86/100
25%
Value4.4 s
73/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.7 s
97/100
10%
715 ms
162 ms
592 ms
9 ms
9 ms
Our browser made a total of 173 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Dumblr.com, 45% (78 requests) were made to Dumbanddumber.com and 23% (39 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.6 sec) relates to the external source Universalpictures.com.
Page size can be reduced by 223.4 kB (17%)
1.3 MB
1.1 MB
In fact, the total size of Dumblr.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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 37.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. This page needs HTML code to be minified as it can gain 6.3 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.7 kB or 77% of the original size.
Potential reduce by 69.7 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. Dumblr images are well optimized though.
Potential reduce by 98.5 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 98.5 kB or 60% of the original size.
Potential reduce by 17.6 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. Dumblr.com needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 80% of the original size.
Number of requests can be reduced by 68 (42%)
163
95
The browser has sent 163 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dumblr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
dumblr.com
715 ms
www.dumblr.com
162 ms
www.dumbanddumber.com
592 ms
reset.css
9 ms
slick.css
9 ms
stylesheet.css
9 ms
buylinks.css
11 ms
modernizr.js
11 ms
jquery-1.11.0.min.js
5 ms
jquery-migrate-1.2.1.min.js
4 ms
slick.min.js
59 ms
global3.js
61 ms
s_wrapper.js
63 ms
slf.js
64 ms
analytics.js
50 ms
gtm.js
94 ms
player.html
784 ms
bkg_gradient_sm.jpg
488 ms
signup.png
17 ms
bkg_nav.gif
241 ms
nav_divider.png
103 ms
ownit_post.png
17 ms
bd.png
72 ms
dvd.png
248 ms
dd.png
391 ms
ondemand.png
243 ms
amazon.png
242 ms
target.png
244 ms
bestbuy.png
245 ms
walmart.png
245 ms
digital-itunes.png
246 ms
digital-amazon.png
247 ms
digital-sony.png
249 ms
digital-google.png
249 ms
digital-vudu.png
249 ms
digital-verizon.png
250 ms
digital-cinemanow.png
250 ms
digital-target.png
251 ms
digital-xbox.png
252 ms
digital-xfinity.png
253 ms
ondemand-verizon.png
255 ms
ondemand-timewarner.png
254 ms
ondemand-directtv.png
256 ms
ondemand-mod.png
258 ms
ondemand-dishcinema.png
257 ms
ondemand-cox.png
260 ms
ondemand-xfinity.png
262 ms
ondemand-uverse.png
261 ms
ondemand-charter.png
261 ms
ondemand-optimum.png
258 ms
s_code.js
260 ms
mod_header.png
418 ms
mod_bodyoutline.gif
454 ms
bkg_module.jpg
403 ms
watch-anytime.png
338 ms
likebox.php
401 ms
bkg_gallery.jpg
453 ms
collect
27 ms
collect.js
26 ms
collect.js
18 ms
lb
33 ms
adServerESI.aspx
326 ms
activityi;src=1538376;type=2014z920;cat=dumba639;ord=3125009977934;~oref=http%3A%2F%2Fwww.dumbanddumber.com%2F
55 ms
activityi;src=1400366;type=dumba839;cat=dumba167;ord=9033096614480;~oref=http%3A%2F%2Fwww.dumbanddumber.com%2F
47 ms
activityi;src=4480452;type=dumbl253;cat=dumbl406;ord=1891990574566;~oref=http%3A%2F%2Fwww.dumbanddumber.com%2F
54 ms
img1.jpg
323 ms
track_page_view
49 ms
track_page_view
55 ms
i.cid
252 ms
LightningBolt.js
70 ms
0
66 ms
utag.js
458 ms
x71.html
35 ms
img2.jpg
189 ms
img3.jpg
188 ms
img4.jpg
188 ms
img5.jpg
193 ms
img6.jpg
190 ms
img7.jpg
193 ms
img8.jpg
193 ms
bkg_synopsis.jpg
373 ms
img_synopsis.jpg
209 ms
bkg_cast.jpg
325 ms
cast_jim-carrey.png
219 ms
cast_kathleen-turner.png
218 ms
cast_jeff-daniels.png
219 ms
cast_laurie-holden.png
219 ms
bkg_tech.jpg
369 ms
hdr_related.gif
329 ms
hdr_related.jpg
332 ms
rel_bruce-almighty.jpg
325 ms
rel_liar-liar.jpg
327 ms
rel_happy-gilmore.jpg
329 ms
rel_billy-madison.jpg
329 ms
jquery.min.js
96 ms
universal.jpg
327 ms
pg13.png
328 ms
fbds.js
144 ms
oct.js
99 ms
btn_arrow-slideshowleft.gif
309 ms
btn_arrow-slideshowright.gif
302 ms
ajax-loader.gif
391 ms
btn_arrow-photogalleryleft.png
373 ms
btn_arrow-photogalleryright.png
338 ms
activityi;src=1538376;type=2012a699;cat=mamaj547;ord=3452565448824.3164
35 ms
slick.woff
448 ms
adsct
97 ms
adsct
62 ms
x18550r8467197
59 ms
s62338889313396
55 ms
imp
27 ms
ebiMDO3r-8l.css
284 ms
jGc-59L_9lo.css
355 ms
6qHpHChjY_J.css
423 ms
uVjHKJ0glvg.css
552 ms
k5BhlqovqZn.css
487 ms
ztINr5qMqM_.css
574 ms
ZY-3seVVf0G.css
559 ms
W9IvqTWpWa9.css
488 ms
QnQTU9p4OI_.js
588 ms
Yuj_Y8xNH2C.js
686 ms
Mpe38fuBVZ2.js
607 ms
n8qIhCw3vMx.js
620 ms
QKy94bWvcbp.js
623 ms
d20DxWMAn1e.js
625 ms
qcMicXoOToy.js
822 ms
57RpJa05x58.js
701 ms
7B-2ZS3Qt8r.js
755 ms
pf3FNnit_ev.js
700 ms
BmFj6FmaQGO.js
701 ms
hGrOQrzI1QD.js
751 ms
qf1RiuO5N-I.js
761 ms
6q5od22S-uf.js
762 ms
OgxH-jlaKMd.js
763 ms
vnY_jgcOCcS.js
885 ms
4ALP2bcCEZ5.js
882 ms
CqFyjqic8Gy.js
884 ms
AmlxWlqMvlv.js
897 ms
cVut-tmssw-.js
882 ms
cExDZPRI9VL.js
958 ms
22 ms
pixel
15 ms
i.match
83 ms
pixel
14 ms
i.match
79 ms
0
8 ms
tpPdk.js
6588 ms
main.css
6021 ms
10980711_940187162666747_53710110597852502_n.png
491 ms
10857945_903290199689777_1989215837894958043_n.jpg
547 ms
11796246_1687257518195133_6843515459264241734_n.jpg
617 ms
11203073_10153202225236210_2762219989396940769_n.jpg
741 ms
12509484_1666200476987896_4271866824859624570_n.jpg
683 ms
1934412_101890443525864_4922436414318463261_n.jpg
749 ms
12376084_527360860761544_3635213379543483319_n.jpg
744 ms
11051805_778276805651283_5170527897917551585_n.jpg
723 ms
11222943_508652085958824_6194956079587395392_n.jpg
713 ms
10647062_1097786883573440_2057081888520987985_n.jpg
816 ms
12249670_1077051245647004_7732263836141247448_n.jpg
780 ms
12103404_1072583669427095_2131778819_n.jpg
791 ms
12196263_1071714432847352_9164136298279033846_n.jpg
807 ms
11053537_950513441634119_170042936953727369_n.jpg
876 ms
HEyyDkPknAC.png
126 ms
wL6VQj7Ab77.png
127 ms
s7jcwEQH7Sx.png
130 ms
QDwYpIaRyfG.png
128 ms
l5aPruN9xMM.png
130 ms
K00K-UgnsKu.png
128 ms
yCfZpessXwm.js
70 ms
gxbPuQdXIZP.png
69 ms
K_65vAc89SX.png
70 ms
VXcANLwwL5J.js
69 ms
22 ms
dumblr.com accessibility score
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
dumblr.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
General
Impact
Issue
Detected JavaScript libraries
dumblr.com SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dumblr.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Dumblr.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.
dumblr.com
Open Graph data is detected on the main page of Dumblr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: