5.1 sec in total
1.6 sec
3.1 sec
416 ms
Visit textfails.com now to see the best up-to-date Textfails content and also check out these interesting facts you probably never knew about textfails.com
Funny texts and failed auto correct SMS, submitted by real people.
Visit textfails.comWe analyzed Textfails.com page load time and found that the first response time was 1.6 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
textfails.com performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value1.6 s
99/100
25%
Value1.1 s
100/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value1.1 s
100/100
10%
1607 ms
132 ms
134 ms
135 ms
137 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 36% of them (39 requests) were addressed to the original Textfails.com, 21% (23 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Textfails.com.
Page size can be reduced by 484.4 kB (48%)
1.0 MB
533.0 kB
In fact, the total size of Textfails.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 536.3 kB which makes up the majority of the site volume.
Potential reduce by 92.7 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 92.7 kB or 79% of the original size.
Potential reduce by 40.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, Textfails needs image optimization as it can save up to 40.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 338.8 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 338.8 kB or 63% of the original size.
Potential reduce by 12.8 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. Textfails.com needs all CSS files to be minified and compressed as it can save up to 12.8 kB or 77% of the original size.
Number of requests can be reduced by 62 (60%)
104
42
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Textfails. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
textfails.com
1607 ms
style.css
132 ms
speechballoons.css
134 ms
output.css
135 ms
styles.css
137 ms
postratings-css.css
135 ms
style.min.css
197 ms
pagenavi-css.css
194 ms
jquery.js
319 ms
tdomf-style-form.css
199 ms
show_ads.js
8 ms
addthis_widget.js
48 ms
jquery.form.min.js
81 ms
scripts.js
115 ms
postratings-js.js
140 ms
bg_body.gif
125 ms
bg_header_bottom.gif
126 ms
bg_header_top.gif
126 ms
bg_title_bottom.gif
126 ms
bg_title_top.gif
126 ms
header.gif
200 ms
icon_rss.gif
200 ms
bg_rc_top.jpg
199 ms
bg_date_button.jpg
199 ms
Plug-her-into-a-cooter.jpg
210 ms
bg_rc_bottom.gif
200 ms
rating_on.gif
238 ms
rating_half.gif
239 ms
rating_off.gif
238 ms
loading.gif
239 ms
Mom-and-the-stiffy.jpg
295 ms
3-e1361064295569.jpg
455 ms
8-e1361064202727.png
488 ms
zrt_lookup.html
41 ms
show_ads_impl.js
48 ms
ads
200 ms
osd.js
124 ms
ads
222 ms
ads
322 ms
bg_sidebar_rc_top.jpg
156 ms
bg_sidebar_rc_bottom.gif
162 ms
bg_dotted.gif
161 ms
bg_sidebar_rc_search_top.gif
205 ms
bg_sidebar_rc_search_bottom.gif
228 ms
bg_searchform.gif
236 ms
bg_footer.gif
231 ms
rating_over.gif
248 ms
all.js
29 ms
300lo.json
47 ms
sh.8e5f85691f9aaa082472a194.html
17 ms
ie67-css.d5089428ac7f05efd372.js
43 ms
counter-ie.033ee35c761079a6df0d.js
34 ms
likebox.php
262 ms
tbc04.gif
40 ms
shares.json
52 ms
shares.json
51 ms
shares.json
50 ms
shares.json
57 ms
shares.json
49 ms
187 ms
xd_arbiter.php
27 ms
xd_arbiter.php
48 ms
m_js_controller.js
42 ms
abg.js
57 ms
nsc01.gif
29 ms
googlelogo_color_112x36dp.png
81 ms
nessie_icon_magazine_black.png
73 ms
nessie_icon_magazine_white.png
74 ms
s
58 ms
x_button_blue2.png
52 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
3 ms
McLpmVM3wCm.css
17 ms
VH4VPudaxfN.css
20 ms
q68gy-v_YMF.js
31 ms
FJmpeSpHpjS.js
59 ms
0wM5s1Khldu.js
70 ms
1bNoFZUdlYZ.js
73 ms
150533_146576662058245_6338342_n.jpg
45 ms
10247283_1578783505679091_1352496568_n.jpg
8 ms
12119006_846870862111647_583562071312317971_n.jpg
9 ms
12734073_880881185343360_2895483538292681304_n.jpg
11 ms
wL6VQj7Ab77.png
6 ms
s7jcwEQH7Sx.png
7 ms
I6-MnjEovm5.js
28 ms
pQrUxxo5oQp.js
28 ms
ui
31 ms
comments.php
143 ms
comments.php
175 ms
comments.php
617 ms
comments.php
501 ms
comments.php
502 ms
xd_arbiter.php
10 ms
FhnPlz7pUCL.css
6 ms
X97l7PURgJ9.css
9 ms
LTv6ZK-5zxz.js
68 ms
1FCa-btixu2.js
32 ms
Oagsvfb4VWi.js
31 ms
FyxLoiww5bU.js
35 ms
HaMjR2eXz4B.js
67 ms
WN2wSsLOuKy.js
111 ms
HgJbVwzBr8E.js
118 ms
Q4A0UyjU8W2.js
120 ms
OZFAYTv-ZUg.js
190 ms
fav.png
191 ms
odA9sNLrE86.jpg
190 ms
K00K-UgnsKu.png
189 ms
408719_172198336220820_1065887925_n.jpg
69 ms
textfails.com accessibility score
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
textfails.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
textfails.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Textfails.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Textfails.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.
textfails.com
Open Graph data is detected on the main page of Textfails. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: