11.5 sec in total
159 ms
11 sec
386 ms
Welcome to diddydirtymoney.com homepage info - get ready to check Diddydirtymoney best content right away, or after learning these important things about diddydirtymoney.com
Linktree. Make your link do more.
Visit diddydirtymoney.comWe analyzed Diddydirtymoney.com page load time and found that the first response time was 159 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
diddydirtymoney.com performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value11.6 s
0/100
25%
Value8.0 s
21/100
10%
Value2,380 ms
5/100
30%
Value0.047
99/100
15%
Value11.3 s
19/100
10%
159 ms
70 ms
490 ms
31 ms
265 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Diddydirtymoney.com, 69% (66 requests) were made to Puffdaddyandthefamily.com and 13% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (8.6 sec) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 2.4 MB (40%)
6.1 MB
3.7 MB
In fact, the total size of Diddydirtymoney.com main page is 6.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. 75% 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 3.2 MB which makes up the majority of the site volume.
Potential reduce by 34.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 34.2 kB or 80% of the original size.
Potential reduce by 84.5 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. Diddydirtymoney images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 71% of the original size.
Potential reduce by 1.3 MB
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. Diddydirtymoney.com needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 90% of the original size.
Number of requests can be reduced by 52 (66%)
79
27
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Diddydirtymoney. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
diddydirtymoney.com
159 ms
www.diddy.com
70 ms
puffdaddyandthefamily.com
490 ms
css
31 ms
frontend.css
265 ms
responsive.css
357 ms
layerslider.css
1378 ms
css
60 ms
styles.css
213 ms
style.css
371 ms
font-awesome.min.css
159 ms
style.min.css
252 ms
stylesheet.min.css
572 ms
webkit_stylesheet.css
344 ms
safari_stylesheet.css
539 ms
style_dynamic.css
458 ms
responsive.min.css
651 ms
style_dynamic_responsive.css
651 ms
js_composer.css
685 ms
custom_css.css
810 ms
css
48 ms
puffdaddyandthefamily.com
766 ms
jquery.min.js
49 ms
frontend.js
952 ms
greensock.js
996 ms
layerslider.kreaturamedia.jquery.js
832 ms
layerslider.transitions.js
1002 ms
external-tracking.min.js
1092 ms
jquery.form.min.js
915 ms
scripts.js
998 ms
ssba.min.js
1233 ms
qode-like.min.js
1283 ms
plugins.js
1432 ms
jquery.carouFredSel-6.2.1.min.js
1304 ms
lemmon-slider.min.js
1443 ms
jquery.fullPage.min.js
1569 ms
jquery.mousewheel.min.js
1624 ms
jquery.touchSwipe.min.js
1568 ms
isotope.pkgd.min.js
1737 ms
js
93 ms
default_dynamic.js
1459 ms
default.min.js
1905 ms
custom_js.js
1563 ms
comment-reply.min.js
1618 ms
ajax.min.js
1763 ms
js_composer_front.js
1713 ms
wp-embed.min.js
1696 ms
count.js
1451 ms
wp-emoji-release.min.js
1578 ms
analytics.js
35 ms
style.css
739 ms
1444801243_b26f95e447d016e530fe41f83566bbc2-300x300.jpg
31 ms
newbadboy.png
735 ms
newnewnnw.png
739 ms
pixel-video.png
739 ms
newpuff.jpg
1023 ms
CS-n7KgUwAIS04P-e1446669018627.jpg
833 ms
btn-listen-sc-s.png
736 ms
Get_it_on_iTunes_Badge_US_11141.png
866 ms
finnagetlooseartworkfinal.jpg
817 ms
ross-diddy-french-500x500.jpg
924 ms
FullSizeRender-500x500.jpg
1073 ms
puffchrisrock-500x500.jpg
896 ms
kim-500x500.jpg
1359 ms
styples-p-500x500.jpg
1176 ms
puffandthefamily-500x500.jpg
971 ms
puff-daddy-blow-a-check-video-1-500x500.jpg
1162 ms
puff-daddy-blow-a-check-video-500x500.jpg
1053 ms
puff-1-500x500.jpg
1434 ms
puffpuff-500x500.jpg
1127 ms
jointhebadboyfamily.jpg
2173 ms
ga.js
120 ms
collect
57 ms
puffpuffkate2.jpg
1442 ms
puff-daddy-and-the-family-mmm-background.jpg
1816 ms
finnagetloosebackground.jpg
1791 ms
ZKwULyCG95tk6mOqHQfRBC3USBnSvpkopQaUR-2r7iU.ttf
48 ms
cbAbzEjxTdN5KKmS-gA0tS3USBnSvpkopQaUR-2r7iU.ttf
80 ms
rr0ijB5_2nAJsAoZ6vECXaCWcynf_cDxXwCLxiixG1c.ttf
81 ms
do7-0avPC2vxor6SN2THGA.ttf
113 ms
Li18TEFObx_yGdzKDoI_ci3USBnSvpkopQaUR-2r7iU.ttf
113 ms
STBOO2waD2LpX45SXYjQBS3USBnSvpkopQaUR-2r7iU.ttf
114 ms
WmVKXVcOuffP_qmCpFuyzS3USBnSvpkopQaUR-2r7iU.ttf
114 ms
QoPu455RxV2raYSIFXAMBS3USBnSvpkopQaUR-2r7iU.ttf
110 ms
Ji5epXNcpHu3r63lhS0cTi3USBnSvpkopQaUR-2r7iU.ttf
114 ms
fontawesome-webfont.woff
1688 ms
6q1c0ofG6NKsEhAc2eh-3V02b4v3fUxqf9CZJ1qUoIA.ttf
8612 ms
TVSB8ogXDKMcnAAJ5CqrUtqQynqKV_9Plp7mupa0S4g.ttf
114 ms
7dO2Hj7qB8nRVFK0svQqRqCWcynf_cDxXwCLxiixG1c.ttf
112 ms
__utm.gif
36 ms
count.js
204 ms
common.js
22 ms
util.js
48 ms
stats.js
35 ms
AuthenticationService.Authenticate
17 ms
diddydirtymoney.com accessibility score
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
ARIA IDs are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
diddydirtymoney.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
Missing source maps for large first-party JavaScript
diddydirtymoney.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diddydirtymoney.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 Diddydirtymoney.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.
diddydirtymoney.com
Open Graph description is not detected on the main page of Diddydirtymoney. 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: