930 ms in total
26 ms
686 ms
218 ms
Visit notmuch.com now to see the best up-to-date Notmuch content for United States and also check out these interesting facts you probably never knew about notmuch.com
Michael Feldman's Whad'ya Know Archive 1985-2016
Visit notmuch.comWe analyzed Notmuch.com page load time and found that the first response time was 26 ms and then it took 904 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster. This domain responded with an error, which can significantly jeopardize Notmuch.com rating and web reputation
notmuch.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.1 s
46/100
25%
Value10.7 s
7/100
10%
Value8,360 ms
0/100
30%
Value0.137
80/100
15%
Value25.6 s
0/100
10%
26 ms
38 ms
9 ms
14 ms
8 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 89% of them (47 requests) were addressed to the original Notmuch.com, 4% (2 requests) were made to S7.addthis.com and 2% (1 request) were made to Googletagservices.com. The less responsive or slowest element that took the longest time to load (396 ms) belongs to the original domain Notmuch.com.
Page size can be reduced by 873.6 kB (57%)
1.5 MB
653.9 kB
In fact, the total size of Notmuch.com main page is 1.5 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. 65% of websites need less resources to load. HTML takes 568.5 kB which makes up the majority of the site volume.
Potential reduce by 415.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 415.3 kB or 73% of the original size.
Potential reduce by 28.8 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. Notmuch images are well optimized though.
Potential reduce by 326.1 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 326.1 kB or 65% of the original size.
Potential reduce by 103.4 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. Notmuch.com needs all CSS files to be minified and compressed as it can save up to 103.4 kB or 84% of the original size.
Number of requests can be reduced by 13 (27%)
49
36
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Notmuch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
notmuch.com
26 ms
www.notmuch.com
38 ms
css__BJ6Ou6QsBRtnFTmxaakamOIS8n4QswDP2XnnZ1sxtaM__NBuvkP6eInGIkb1aJvUHx5PX79XApuxBDkk_77W5tYk__y-32R79m-0h0Syo7BQdXHBsxKv_g6iWJzptByHonFV4.css
9 ms
css__YVwgRf5eqBQr5e2zW-b9uAnSwUcPS9fsVzeNqERHd60__TUo9Mv_NYjK3hnPhdYYCgMhxSYMgi7y-CuoR5Hkzl4o__y-32R79m-0h0Syo7BQdXHBsxKv_g6iWJzptByHonFV4.css
14 ms
css__6mYXCiTUOTRtybGKA-pvZbtDO8TEc3wemtuIXLgqWfY__R74vQmPvkyXCLnmR-hyvfKJKEBpNk5rI70MWOKm_8OQ__y-32R79m-0h0Syo7BQdXHBsxKv_g6iWJzptByHonFV4.css
8 ms
css__6WKjh5y5MLpWaZK-RmChOn5akS4jOOyiqMTcwrHaEEo__TnF8V34ZmslQXK0x58A3RAVH_lujiIfwEGo_HV-8LJ8__y-32R79m-0h0Syo7BQdXHBsxKv_g6iWJzptByHonFV4.css
12 ms
css__5kL433sdOn2JbRM8XOA7oaLjGB20uipjvyOr1KowC6I__yj_-uzHxfiKmx87y9J9_7ndGkNtu59Hryaljl8euOnA__y-32R79m-0h0Syo7BQdXHBsxKv_g6iWJzptByHonFV4.css
13 ms
js__UiO29A8qiU-liB_96gCC8E9JKDzRn317nHrd6s0stps__JjoPzCkzYa71IxBF0sXb6yVSB5ojjxYZ6gppRP-xCds__y-32R79m-0h0Syo7BQdXHBsxKv_g6iWJzptByHonFV4.js
20 ms
js__pTIVy7WjvR5durRd2UipqEO0681oaHpJVAwquVlqIuU___FC1CKpBQxG877MQHqb5sQ_jKHuM5JK2Y0-lwl3riuQ__y-32R79m-0h0Syo7BQdXHBsxKv_g6iWJzptByHonFV4.js
18 ms
js__eWVT8rQC8oMbKGKL28inNrj0Dk_nECos7YpajDs-fs0__Sl1IQ_wZhOxcX3baj9dYlTx0JmVqPuZVBtiZcf4ZPkQ__y-32R79m-0h0Syo7BQdXHBsxKv_g6iWJzptByHonFV4.js
17 ms
js__9h3p1XZ7jrZJdtMJkhDHDbEkXCUgfMbu58H2Q7yYgNM__Wum8ZRaFDf4HJbZGDVDNSoxt1-JmwOrrAVSP3vHBDLI__y-32R79m-0h0Syo7BQdXHBsxKv_g6iWJzptByHonFV4.js
17 ms
addthis_widget.js
54 ms
analytics.js
389 ms
gpt.js
370 ms
menu-background.gif
377 ms
WYK_Logo_White.png
377 ms
pri_logo_w.png
380 ms
WPRLogo_white_WYK.png
380 ms
twitter.png
374 ms
facebook.png
380 ms
Banner_Images.jpg
384 ms
search.gif
380 ms
PRI_color.png
383 ms
WPRlogo_color_ttbook_0.png
389 ms
menu-active-item.jpg
380 ms
arrow-down.png
387 ms
star-rule.gif
380 ms
150131_phox_1.jpg
391 ms
photo-frame.png
382 ms
add-sm.png
383 ms
download-sm.png
384 ms
Ticket.png
387 ms
read-more.jpg
384 ms
160305_rich.jpeg
389 ms
160319_bryson_0.jpg
392 ms
160423_venue_1.jpg
390 ms
MF_web_112013_11.jpg
386 ms
150117_hale2_0.jpg
390 ms
150307_Duchovny_0.jpg
392 ms
150804_wallace.jpg
394 ms
141108_marx_2.jpg
395 ms
150919_kindler_0.jpeg
392 ms
150804_vonnegut.jpg
396 ms
150718_Daly_1.jpg
393 ms
footer-graphic.png
396 ms
widgets.js
227 ms
300lo.json
123 ms
previous.gif
120 ms
next.gif
121 ms
footer.jpg
121 ms
american_purpose-webfont.ttf
138 ms
sh.7c7179124ea24ac6ba46caac.html
135 ms
pubads_impl_81.js
135 ms
notmuch.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
notmuch.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
notmuch.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Notmuch.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 Notmuch.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.
notmuch.com
Open Graph description is not detected on the main page of Notmuch. 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: