10.9 sec in total
2.7 sec
8.1 sec
61 ms
Click here to check amazing Duck And Craig content. Otherwise, check out these important facts you probably never knew about duckandcraig.com
Visit duckandcraig.comWe analyzed Duckandcraig.com page load time and found that the first response time was 2.7 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
duckandcraig.com performance score
name
value
score
weighting
Value14.2 s
0/100
10%
Value21.6 s
0/100
25%
Value38.2 s
0/100
10%
Value1,330 ms
17/100
30%
Value0.021
100/100
15%
Value22.8 s
1/100
10%
2746 ms
291 ms
631 ms
761 ms
760 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 68% of them (44 requests) were addressed to the original Duckandcraig.com, 15% (10 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Duckandcraig.com.
Page size can be reduced by 81.6 kB (28%)
286.4 kB
204.8 kB
In fact, the total size of Duckandcraig.com main page is 286.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 117.4 kB which makes up the majority of the site volume.
Potential reduce by 41.0 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 41.0 kB or 78% of the original size.
Potential reduce by 1.1 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. Obviously, Duck And Craig needs image optimization as it can save up to 1.1 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 32.2 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 32.2 kB or 27% of the original size.
Potential reduce by 7.2 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. Duckandcraig.com has all CSS files already compressed.
Number of requests can be reduced by 47 (87%)
54
7
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duck And Craig. 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 17 to 1 for CSS and as a result speed up the page load time.
duckandcraig.com
2746 ms
wp-emoji-release.min.js
291 ms
style.min.css
631 ms
theme.min.css
761 ms
style.css
760 ms
style.min.css
792 ms
elementor-icons.min.css
835 ms
frontend-legacy.min.css
808 ms
frontend.min.css
924 ms
post-1055.css
1090 ms
frontend.min.css
1357 ms
global.css
1099 ms
post-1030.css
1138 ms
css
31 ms
fontawesome.min.css
1131 ms
solid.min.css
1215 ms
jquery.min.js
1625 ms
jquery-migrate.min.js
1386 ms
js
54 ms
css
29 ms
animations.min.css
1513 ms
rs6.css
1448 ms
rbtools.min.js
1767 ms
rs6.min.js
1884 ms
jquery.smartmenus.min.js
1700 ms
webpack-pro.runtime.min.js
1731 ms
webpack.runtime.min.js
1804 ms
frontend-modules.min.js
1883 ms
regenerator-runtime.min.js
1977 ms
wp-polyfill.min.js
2009 ms
hooks.min.js
2058 ms
i18n.min.js
2079 ms
frontend.min.js
2141 ms
waypoints.min.js
2196 ms
core.min.js
2254 ms
swiper.min.js
2561 ms
share-link.min.js
2339 ms
dialog.min.js
2371 ms
frontend.min.js
2408 ms
preloaded-elements-handlers.min.js
2477 ms
preloaded-modules.min.js
2245 ms
jquery.sticky.min.js
1993 ms
underscore.min.js
1910 ms
wp-util.min.js
1928 ms
frontend.min.js
1974 ms
gtm.js
45 ms
Logo_white_small-1-op12fo87vipg3fu44t7k3kndpl4pc6opw44jg7jzcs.png
1163 ms
dummy.png
1218 ms
analytics.js
39 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
36 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
60 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
55 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
58 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
47 ms
js
41 ms
collect
41 ms
conversion_async.js
37 ms
collect
39 ms
78 ms
38 ms
duckandcraig.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
Image elements do not have [alt] attributes
duckandcraig.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
duckandcraig.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Duckandcraig.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 Duckandcraig.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.
duckandcraig.com
Open Graph description is not detected on the main page of Duck And Craig. 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: