1.5 sec in total
89 ms
984 ms
402 ms
Visit doubleday.com now to see the best up-to-date Doubleday content and also check out these interesting facts you probably never knew about doubleday.com
Visit doubleday.comWe analyzed Doubleday.com page load time and found that the first response time was 89 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
doubleday.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value7.9 s
3/100
25%
Value6.8 s
34/100
10%
Value230 ms
86/100
30%
Value0.132
81/100
15%
Value14.8 s
8/100
10%
89 ms
85 ms
43 ms
41 ms
43 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Doubleday.com, 32% (29 requests) were made to Knopfdoubleday.com and 29% (26 requests) were made to Randomhouse.com. The less responsive or slowest element that took the longest time to load (422 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 964.1 kB (39%)
2.4 MB
1.5 MB
In fact, the total size of Doubleday.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. 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 103.3 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 103.3 kB or 79% of the original size.
Potential reduce by 408.6 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, Doubleday needs image optimization as it can save up to 408.6 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 380.0 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 380.0 kB or 65% of the original size.
Potential reduce by 72.1 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. Doubleday.com needs all CSS files to be minified and compressed as it can save up to 72.1 kB or 79% of the original size.
Number of requests can be reduced by 42 (50%)
84
42
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doubleday. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
doubleday.com
89 ms
85 ms
core.css
43 ms
tablet.css
41 ms
desktop.css
43 ms
rgc.css
37 ms
font-awesome.min.css
37 ms
jquery.min.js
23 ms
galleria.min.js
56 ms
wicked.min.js
34 ms
kdd.js
55 ms
5817ee6e-ab40-40fc-ab33-a19d9e79bd7b.js
67 ms
emv-2-0.js
102 ms
jquery.js
63 ms
View.sitemeta.js
37 ms
View.Analytics.Model.js
37 ms
View.Analytics.Tracker.js
35 ms
View.Analytics.Controller.js
45 ms
kdd-preferences.js
35 ms
conversion.js
36 ms
bg.jpg
10 ms
all.js
269 ms
logo-doubleday-176x250.png
63 ms
ScriptPackage.ashx
275 ms
utag.js
100 ms
dc.js
36 ms
icon-search-tiny.png
32 ms
arrow-down-blk.png
29 ms
col-divider.png
31 ms
arrow-more.png
30 ms
sprite-social-sm.png
30 ms
arrow-icon.png
31 ms
DD_PromoBox_732x190_6.gif
32 ms
DD_PromoBox_480x200_6.gif
32 ms
arrow-load.png
31 ms
33 ms
89 ms
86 ms
84 ms
88 ms
86 ms
81 ms
85 ms
89 ms
87 ms
91 ms
90 ms
92 ms
86 ms
90 ms
93 ms
94 ms
91 ms
94 ms
91 ms
92 ms
129 ms
112 ms
93 ms
e56ecb6d-da41-4bd9-982d-2d295bec9ab0.woff
68 ms
sprite-imprints-sm.png
59 ms
arrow_tiny_sort.png
58 ms
66 ms
analytics.js
47 ms
__utm.gif
56 ms
mrseaves.woff
56 ms
9c69c878-2255-4027-8632-ed3635cddf45.woff
56 ms
prh-pptou-2015.js
15 ms
utag.198.js
22 ms
utag.199.js
37 ms
utag.158.js
30 ms
utag.188.js
22 ms
utag.200.js
49 ms
collect
21 ms
49 ms
conversion_async.js
21 ms
quant.js
16 ms
fbevents.js
129 ms
pixel;r=1210637347;a=p-HqMxwjcwxcXJG;fpan=1;fpa=P0-1590764319-1458292170513;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458292170512;tzo=-180;ref=;url=http%3A%2F%2Fknopfdoubleday.com%2Fimprint%2Fdoubleday%2F;ogl=title.%2Ctype.article%2Curl.%2Cdescription.%2Csite_name.Knopf%20Doubleday
14 ms
17 ms
collect
12 ms
18 ms
96 ms
xd_arbiter.php
217 ms
xd_arbiter.php
422 ms
7 ms
pinit.js
13 ms
newsletters.css
10 ms
newsletters.css
10 ms
pinit_main.js
46 ms
doubleday.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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
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.
doubleday.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
Browser errors were logged to the console
doubleday.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
Image elements do not have [alt] attributes
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doubleday.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Doubleday.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.
doubleday.com
Open Graph description is not detected on the main page of Doubleday. 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: