4.2 sec in total
207 ms
3.6 sec
412 ms
Click here to check amazing Patdudley content. Otherwise, check out these important facts you probably never knew about patdudley.com
Visit patdudley.comWe analyzed Patdudley.com page load time and found that the first response time was 207 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
patdudley.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.0 s
13/100
25%
Value6.4 s
41/100
10%
Value920 ms
30/100
30%
Value0.683
7/100
15%
Value8.1 s
42/100
10%
207 ms
446 ms
983 ms
571 ms
371 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 15% of them (22 requests) were addressed to the original Patdudley.com, 68% (102 requests) were made to Kit-pro.fontawesome.com and 6% (9 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Patdudley.com.
Page size can be reduced by 473.4 kB (25%)
1.9 MB
1.4 MB
In fact, the total size of Patdudley.com main page is 1.9 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.1 MB which makes up the majority of the site volume.
Potential reduce by 51.5 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 51.5 kB or 78% of the original size.
Potential reduce by 24.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. Patdudley images are well optimized though.
Potential reduce by 26.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 26.5 kB or 65% of the original size.
Potential reduce by 370.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. Patdudley.com needs all CSS files to be minified and compressed as it can save up to 370.5 kB or 59% of the original size.
Number of requests can be reduced by 13 (33%)
39
26
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Patdudley. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
patdudley.com
207 ms
www.patdudley.com
446 ms
template.css
983 ms
compiled.css
571 ms
default-font-group.css
371 ms
88923_324201162134PM59044.jpg
1092 ms
all.min.js
665 ms
custom.min.js
415 ms
130259_11232016100333AM21715.jpg
916 ms
130259_11232016100424AM78373.jpg
916 ms
130259_11232016100412AM36288.jpg
1079 ms
RL01.gif
1088 ms
RL02.gif
1514 ms
RL03.gif
1588 ms
jquery.dataTables.min.css
116 ms
all.css
127 ms
142193_1214201890620AM36750.jpg
1012 ms
fa-solid-900.woff
225 ms
fa-regular-400.woff
272 ms
pro-fa-solid-900-5.15.1.woff
311 ms
pro-fa-solid-900-5.14.0.woff
348 ms
pro-fa-solid-900-5.13.0.woff
416 ms
pro-fa-solid-900-5.12.1.woff
406 ms
pro-fa-solid-900-5.12.0.woff
407 ms
pro-fa-solid-900-5.11.2.woff
467 ms
pro-fa-solid-900-5.11.1.woff
409 ms
pro-fa-solid-900-5.11.0.woff
404 ms
pro-fa-solid-900-5.10.2.woff
407 ms
pro-fa-solid-900-5.10.1.woff
407 ms
pro-fa-solid-900-5.9.0.woff
465 ms
pro-fa-solid-900-5.8.2.woff
412 ms
pro-fa-solid-900-5.8.0.woff
467 ms
pro-fa-solid-900-5.7.1.woff
508 ms
pro-fa-solid-900-5.7.0.woff
465 ms
pro-fa-solid-900-5.6.3.woff
472 ms
pro-fa-solid-900-5.6.1.woff
473 ms
pro-fa-solid-900-5.6.0.woff
503 ms
pro-fa-solid-900-5.5.0.woff
507 ms
pro-fa-solid-900-5.4.1.woff
506 ms
pro-fa-solid-900-5.4.0.woff
508 ms
pro-fa-solid-900-5.3.0.woff
541 ms
pro-fa-solid-900-5.2.0.woff
542 ms
pro-fa-solid-900-5.1.1.woff
541 ms
pro-fa-solid-900-5.1.0.woff
552 ms
pro-fa-solid-900-5.0.13.woff
540 ms
pro-fa-solid-900-5.0.11.woff
551 ms
pro-fa-solid-900-5.0.10.woff
690 ms
pro-fa-solid-900-5.0.9.woff
689 ms
pro-fa-solid-900-5.0.7.woff
579 ms
pro-fa-solid-900-5.0.5.woff
645 ms
pro-fa-solid-900-5.0.3.woff
642 ms
pro-fa-solid-900-5.0.1.woff
642 ms
pro-fa-solid-900-5.0.0.woff
685 ms
pro-fa-regular-400-5.15.1.woff
686 ms
pro-fa-regular-400-5.14.0.woff
809 ms
cdata.txt
337 ms
getLead
369 ms
p8fQ1mqO9Nw
334 ms
0.jpg
268 ms
superlative-logo.png
365 ms
getToken
1166 ms
ui-bg_flat_75_ffffff_40x100.png
654 ms
pro-fa-regular-400-5.13.0.woff
487 ms
88923_513201381107AM42547.jpg
440 ms
pro-fa-regular-400-5.12.1.woff
431 ms
pro-fa-regular-400-5.12.0.woff
406 ms
pro-fa-regular-400-5.11.2.woff
406 ms
pro-fa-regular-400-5.11.1.woff
407 ms
pro-fa-regular-400-5.11.0.woff
409 ms
pro-fa-regular-400-5.10.2.woff
407 ms
pro-fa-regular-400-5.10.1.woff
406 ms
pro-fa-regular-400-5.9.0.woff
404 ms
pro-fa-regular-400-5.8.2.woff
387 ms
pro-fa-regular-400-5.8.0.woff
355 ms
pro-fa-regular-400-5.7.1.woff
355 ms
pro-fa-regular-400-5.7.0.woff
351 ms
www-player.css
118 ms
www-embed-player.js
148 ms
base.js
225 ms
fetch-polyfill.js
85 ms
pro-fa-regular-400-5.6.3.woff
349 ms
pro-fa-regular-400-5.6.1.woff
345 ms
pro-fa-regular-400-5.6.0.woff
332 ms
pro-fa-regular-400-5.5.0.woff
315 ms
pro-fa-regular-400-5.4.1.woff
317 ms
pro-fa-regular-400-5.4.0.woff
317 ms
pro-fa-regular-400-5.3.0.woff
314 ms
pro-fa-regular-400-5.2.0.woff
285 ms
pro-fa-regular-400-5.1.1.woff
283 ms
pro-fa-regular-400-5.1.0.woff
282 ms
pro-fa-regular-400-5.0.13.woff
330 ms
pro-fa-regular-400-5.0.11.woff
321 ms
pro-fa-regular-400-5.0.10.woff
320 ms
pro-fa-regular-400-5.0.9.woff
319 ms
pro-fa-regular-400-5.0.7.woff
263 ms
pro-fa-regular-400-5.0.5.woff
227 ms
pro-fa-regular-400-5.0.3.woff
228 ms
pro-fa-regular-400-5.0.1.woff
214 ms
pro-fa-regular-400-5.0.0.woff
187 ms
pro-fa-light-300-5.15.1.woff
184 ms
pro-fa-light-300-5.14.0.woff
186 ms
pro-fa-light-300-5.13.0.woff
78 ms
pro-fa-light-300-5.12.1.woff
71 ms
pro-fa-light-300-5.12.0.woff
71 ms
pro-fa-light-300-5.11.2.woff
71 ms
pro-fa-light-300-5.11.1.woff
70 ms
pro-fa-light-300-5.11.0.woff
69 ms
pro-fa-light-300-5.10.2.woff
69 ms
pro-fa-light-300-5.10.1.woff
70 ms
pro-fa-light-300-5.9.0.woff
71 ms
pro-fa-light-300-5.8.2.woff
69 ms
pro-fa-light-300-5.8.0.woff
66 ms
pro-fa-light-300-5.7.1.woff
67 ms
pro-fa-light-300-5.7.0.woff
68 ms
pro-fa-light-300-5.6.3.woff
172 ms
pro-fa-light-300-5.6.1.woff
171 ms
pro-fa-light-300-5.6.0.woff
168 ms
pro-fa-light-300-5.5.0.woff
169 ms
pro-fa-light-300-5.4.1.woff
205 ms
pro-fa-light-300-5.4.0.woff
204 ms
pro-fa-light-300-5.3.0.woff
213 ms
pro-fa-light-300-5.2.0.woff
212 ms
pro-fa-light-300-5.1.1.woff
213 ms
pro-fa-light-300-5.1.0.woff
212 ms
pro-fa-light-300-5.0.13.woff
306 ms
ad_status.js
193 ms
pro-fa-light-300-5.0.11.woff
192 ms
pro-fa-light-300-5.0.10.woff
258 ms
pro-fa-light-300-5.0.9.woff
191 ms
pro-fa-light-300-5.0.7.woff
192 ms
pro-fa-light-300-5.0.5.woff
190 ms
pro-fa-light-300-5.0.3.woff
256 ms
pro-fa-light-300-5.0.1.woff
255 ms
pro-fa-light-300-5.0.0.woff
256 ms
initplayback
258 ms
embed.js
72 ms
AMLnZu-1NdWorCnlmedmyYraDahnbLWSQ4mxBBRkJM7o=s68-c-k-c0x00ffffff-no-rj
187 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
141 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
149 ms
id
95 ms
Create
52 ms
cdata.txt
128 ms
qoe
15 ms
log_event
1 ms
p8fQ1mqO9Nw
151 ms
0.jpg
56 ms
ad_status.js
68 ms
initplayback
58 ms
Create
86 ms
id
37 ms
patdudley.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.
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
patdudley.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
Missing source maps for large first-party JavaScript
patdudley.com SEO score
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
ZH
C
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Patdudley.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed language. Our system also found out that Patdudley.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
patdudley.com
Open Graph description is not detected on the main page of Patdudley. 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: