2.5 sec in total
828 ms
1.5 sec
231 ms
Visit imnotwordy.com now to see the best up-to-date Imnotwordy content for United States and also check out these interesting facts you probably never knew about imnotwordy.com
2 million civilized humans are lurking around this mediocre blog.
Visit imnotwordy.comWe analyzed Imnotwordy.com page load time and found that the first response time was 828 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
imnotwordy.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value5.7 s
17/100
25%
Value4.9 s
65/100
10%
Value650 ms
46/100
30%
Value0.012
100/100
15%
Value6.3 s
61/100
10%
828 ms
11 ms
19 ms
16 ms
11 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Imnotwordy.com, 21% (12 requests) were made to Static.tumblr.com and 16% (9 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (828 ms) belongs to the original domain Imnotwordy.com.
Page size can be reduced by 698.6 kB (35%)
2.0 MB
1.3 MB
In fact, the total size of Imnotwordy.com main page is 2.0 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. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 97.1 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. This page needs HTML code to be minified as it can gain 27.1 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 97.1 kB or 87% of the original size.
Potential reduce by 106.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. Imnotwordy images are well optimized though.
Potential reduce by 474.7 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 474.7 kB or 68% of the original size.
Potential reduce by 20.3 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. Imnotwordy.com needs all CSS files to be minified and compressed as it can save up to 20.3 kB or 81% of the original size.
Number of requests can be reduced by 15 (29%)
52
37
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imnotwordy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
imnotwordy.com
828 ms
pre_tumblelog.js
11 ms
jquery.min.js
19 ms
masonry.js
16 ms
jquery.infinitescroll.min.js
11 ms
structure.css
16 ms
colrbox.js
11 ms
loaded.js
13 ms
jquery.backstretch.min.js
13 ms
wordy-script.js
13 ms
globe.css
13 ms
tumblelog_post_message_queue.js
9 ms
index.js
61 ms
like_iframe.html
119 ms
tumblr_nxt83mtZkW1qhup4ao1_r1_500.jpg
121 ms
tumblr_o2x9peScuC1qa2g6fo1_500.jpg
220 ms
tumblr_n2edlmtce51qm3r26o1_500.png
111 ms
false
132 ms
impixu
129 ms
impixu
155 ms
impixu
154 ms
x.gif
98 ms
tumblr_o320znXqYB1qf67ddo1_500.jpg
209 ms
tumblr_o35u71p5v81qkegsbo1_400.jpg
193 ms
tumblr_o316be8Nl91qkm8e2o1_500.jpg
180 ms
tumblr_o32n0omZ611qhkf74o1_500.jpg
182 ms
tumblr_nz1hzvTbwT1r5a0kfo1_500.jpg
265 ms
tumblr_nwdqm1YWOl1sodd3to1_500.jpg
109 ms
tumblr_static_5qucwr0435og8k84sos8ow0gs.png
107 ms
image.png
104 ms
tumblr_nx9devFcPl1qhrr0eo1_500.jpg
106 ms
tumblr_o2du52udvm1us8itno1_500.jpg
107 ms
tumblr_o30j8zvRcL1rqr80io1_500.jpg
106 ms
tumblr_o3a3vgBFza1qgiw5to1_500.jpg
105 ms
tumblr_nh3t5124Sq1rpqkdzo1_500.jpg
106 ms
analytics.html
124 ms
icon2.png
43 ms
glober_thin_free-webfont.woff
394 ms
wordy.woff
375 ms
login_check.html
24 ms
tumblr_nl58nzLrms1sd84dro9_r1_540.jpg
36 ms
tumblr_nl58nzLrms1sd84dro4_400.jpg
11 ms
tumblr_nl58nzLrms1sd84dro1_r1_540.jpg
88 ms
tumblr_nl58nzLrms1sd84dro5_540.jpg
142 ms
tumblr_nl58nzLrms1sd84dro8_r1_540.jpg
35 ms
tumblr_nl58nzLrms1sd84dro2_r1_540.jpg
29 ms
tumblr_nl58nzLrms1sd84dro3_400.jpg
29 ms
rapid-3.36.js
43 ms
rapidworker-1.2.js
42 ms
ga.js
51 ms
analytics.js
51 ms
cs.js
78 ms
yql
234 ms
__utm.gif
20 ms
cedexis.radar.js
22 ms
qIIYRU-oROkIk8vfvxw6QvesZW2xOQ-xsNqO47m55DA.woff
20 ms
imnotwordy.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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
imnotwordy.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
imnotwordy.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 Imnotwordy.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 Imnotwordy.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.
imnotwordy.com
Open Graph description is not detected on the main page of Imnotwordy. 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: