2.2 sec in total
484 ms
1.4 sec
230 ms
Welcome to writing.com homepage info - get ready to check Writing best content for United States right away, or after learning these important things about writing.com
Established in 2000, Writing.Com is the online community for writers of all interests and skill levels. Our community breeds creative writing by writers interacting.
Visit writing.comWe analyzed Writing.com page load time and found that the first response time was 484 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.
writing.com performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value5.3 s
21/100
25%
Value2.5 s
98/100
10%
Value630 ms
47/100
30%
Value0
100/100
15%
Value5.3 s
72/100
10%
484 ms
39 ms
146 ms
25 ms
27 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 29% of them (29 requests) were addressed to the original Writing.com, 20% (20 requests) were made to Static.xx.fbcdn.net and 18% (18 requests) were made to Images.writing.com. The less responsive or slowest element that took the longest time to load (484 ms) belongs to the original domain Writing.com.
Page size can be reduced by 782.6 kB (62%)
1.3 MB
487.2 kB
In fact, the total size of Writing.com main page is 1.3 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. Javascripts take 812.4 kB which makes up the majority of the site volume.
Potential reduce by 134.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. 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 134.1 kB or 74% of the original size.
Potential reduce by 11.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. Writing images are well optimized though.
Potential reduce by 537.9 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 537.9 kB or 66% of the original size.
Potential reduce by 99.5 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. Writing.com needs all CSS files to be minified and compressed as it can save up to 99.5 kB or 85% of the original size.
Number of requests can be reduced by 59 (65%)
91
32
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Writing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.writing.com
484 ms
jquery-1.10.2.min.js
39 ms
wdcjsX20150904f.js
146 ms
jquery.MetaData.js
25 ms
jquery.rating.js
27 ms
colorbox.css
25 ms
jquery.timeago.js
35 ms
jquery.colorbox-min.js
50 ms
jquery.topzindex.min.js
51 ms
jquery.rating.css
51 ms
jquery.mousewheel.js
50 ms
dropzone.css
51 ms
dropzone.min.js
59 ms
joyride-2.1.css
52 ms
jquery.cookie.js
57 ms
jquery.joyride-2.1.js
58 ms
jquery-ui-1.10.3.min.js
102 ms
jquery-ui-1.10.3.min.css
68 ms
jquery.ui.touch-punch.min.js
71 ms
WdCEditor.js
181 ms
styleX-2015-07-16b.css
193 ms
ga.js
9 ms
pl-top.png
32 ms
pl-icon-regular-2.png
29 ms
pl-bottom.gif
31 ms
ribbonb.png
50 ms
badge.png
50 ms
nw.gif
27 ms
__utm.gif
14 ms
frontpage-bkgd.jpg
78 ms
addthis_widget.js
13 ms
adsbygoogle.js
71 ms
wdc-frontpage.gif
75 ms
frontpage-freetojoin2.gif
76 ms
Icon.png
69 ms
en_US
159 ms
show_ads.js
22 ms
bullet.png
19 ms
frontpage-bookshelf.gif
39 ms
frontpage-continue.gif
21 ms
button-icon-11000-1.gif
21 ms
button-icon-6000-1.gif
21 ms
plaque_circlebook-200.png
38 ms
ribbon1_darkteal-10.png
38 ms
ribbon1_blue-10.png
38 ms
ribbon1_darkviolet-10.png
37 ms
button-icon-15000-1.gif
37 ms
trans.gif
22 ms
1694115.gif
127 ms
trans.gif
22 ms
3-circle.gif
22 ms
ca-pub-6977576864300707.js
36 ms
zrt_lookup.html
45 ms
show_ads_impl.js
55 ms
ads
191 ms
osd.js
5 ms
all.js
49 ms
121 ms
xd_arbiter.php
104 ms
xd_arbiter.php
136 ms
ads
184 ms
300lo.json
52 ms
overlay.png
29 ms
sh.7c7179124ea24ac6ba46caac.html
34 ms
bc_ad.php
250 ms
like_box.php
194 ms
bc_ad.php
308 ms
roNeOY-tz5Y.css
45 ms
UHhaxo8Cs3k.css
53 ms
dbNRhrdsQao.css
68 ms
1ssvpqNRk1L.css
94 ms
O8DK6hTywHD.css
81 ms
_rx8naC75Dy.js
99 ms
x5F9OMjKyLw.js
110 ms
ICDbTSzjQEg.js
76 ms
TTCre3391I0.js
78 ms
njO1TPvGzoR.js
97 ms
b_6HNn_J2BZ.js
117 ms
7cm7D75Y0Sf.js
122 ms
rFmE1g6Dkoz.js
136 ms
336JejShbZp.js
126 ms
s
20 ms
578380_10153131354270433_903345095_n.jpg
93 ms
safe_image.php
92 ms
64861_10151366442005433_965292077_n.jpg
48 ms
12745766_10156527786550433_1038127944680886050_n.jpg
49 ms
12743594_10156527760290433_7858525196328201816_n.jpg
48 ms
wL6VQj7Ab77.png
20 ms
s7jcwEQH7Sx.png
23 ms
QDwYpIaRyfG.png
23 ms
a-ZN6WoEOje.png
20 ms
dropzone.css
16 ms
dropzone.min.js
17 ms
joyride-2.1.css
31 ms
jquery.cookie.js
30 ms
jquery.joyride-2.1.js
30 ms
styleX-2015-07-16b.css
147 ms
I6-MnjEovm5.js
9 ms
vlXaquuXMrr.js
9 ms
__utm.gif
4 ms
writing.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
writing.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
writing.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Writing.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 Writing.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.
writing.com
Open Graph description is not detected on the main page of Writing. 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: