4.8 sec in total
463 ms
3.7 sec
695 ms
Click here to check amazing MOSS content for United States. Otherwise, check out these important facts you probably never knew about moss.fm
Prints and products by Olly Moss
Visit moss.fmWe analyzed Moss.fm page load time and found that the first response time was 463 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Moss.fm rating and web reputation
moss.fm performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value3.5 s
64/100
25%
Value3.1 s
92/100
10%
Value70 ms
99/100
30%
Value0.226
55/100
15%
Value3.3 s
93/100
10%
463 ms
12 ms
11 ms
21 ms
15 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Moss.fm, 17% (13 requests) were made to Static.tumblr.com and 13% (10 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 926.3 kB (37%)
2.5 MB
1.6 MB
In fact, the total size of Moss.fm main page is 2.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. 80% 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.4 MB which makes up the majority of the site volume.
Potential reduce by 87.4 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 28.8 kB, which is 28% 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 87.4 kB or 86% of the original size.
Potential reduce by 167.0 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, MOSS needs image optimization as it can save up to 167.0 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 630.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 630.1 kB or 65% of the original size.
Potential reduce by 41.9 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. Moss.fm needs all CSS files to be minified and compressed as it can save up to 41.9 kB or 84% of the original size.
Number of requests can be reduced by 21 (29%)
73
52
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MOSS. 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.
www.moss.fm
463 ms
pre_tumblelog.js
12 ms
reset.css
11 ms
screen.css
21 ms
fancybox-1.3.1.css
15 ms
swfobject.js
18 ms
jquery-1.6.2.min.js
27 ms
jquery.easing.1.3.js
18 ms
jquery.fancybox-1.3.1.pack.js
19 ms
tumblelog.js
15 ms
prologue-1.20.js
46 ms
tumblelog_post_message_queue.js
24 ms
index.js
84 ms
avatar_e52b999c229c_128.png
189 ms
tumblr_n6msi8UpZN1qhy1pno1_250.jpg
168 ms
tumblr_n9jggaAJ6O1rz2dg6o1_250.jpg
173 ms
tumblr_mm48ciyLYM1rb11wko1_250.jpg
337 ms
tumblr_ntcw4u5IPP1qeqo31o1_250.gif
557 ms
false
173 ms
tumblr_inline_mt8rg29QKP1qde345.png
148 ms
impixu
250 ms
tumblr_inline_mpvdyvm9T31qz4rgp.png
143 ms
tumblr_inline_mpvdagfIwa1qz4rgp.gif
146 ms
tumblr_n2hvkcbQFw1qe5k90o1_250.jpg
143 ms
tumblr_n9u926Yfuy1qeqo31o1_500.png
141 ms
tumblr_n22z6mu9aF1qeqo31o1_r1_500.jpg
141 ms
tumblr_mu1owjNV281qeqo31o1_500.png
140 ms
tumblr_n22ytvRxvA1qehhkqo1_250.png
292 ms
tumblr_mu5bqr2fN31qeqo31o1_500.jpg
293 ms
tumblr_mrfsg8mcqK1qz6f9yo3_500.png
156 ms
tumblr_inline_mqek53YowN1qz4rgp.png
289 ms
tumblr_inline_mqejhhOHFD1qz4rgp.png
287 ms
tumblr_inline_mpvdw2Oj9A1qz4rgp.png
247 ms
tumblr_inline_mpvdxj6ynC1qz4rgp.png
288 ms
impixu
246 ms
sprite.png
139 ms
blank.png
137 ms
widgets.js
171 ms
tweets.js
285 ms
fancybox-x.png
108 ms
fancybox-y.png
108 ms
fancybox.png
108 ms
analytics.html
176 ms
login_check.html
24 ms
like.php
245 ms
tumblr_n3iyfpGy411qeqo31o1_500.jpg
97 ms
tumblr_n3iyfpGy411qeqo31o4_500.jpg
95 ms
tumblr_n3iyfpGy411qeqo31o5_500.jpg
141 ms
tumblr_n3iyfpGy411qeqo31o2_250.jpg
143 ms
tumblr_n3iyfpGy411qeqo31o3_250.jpg
139 ms
like.php
299 ms
avatar_e52b999c229c_40.png
75 ms
iframe_logo.png
69 ms
like.php
236 ms
like.php
236 ms
like.php
237 ms
like.php
237 ms
like.php
198 ms
like.php
257 ms
like.php
263 ms
like.php
256 ms
rapid-3.36.js
82 ms
rapidworker-1.2.js
67 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
216 ms
qeKvIRsJabD.js
2608 ms
LVx-xkvaJ0b.png
2600 ms
ga.js
89 ms
analytics.js
150 ms
cs.js
143 ms
addthis.html
180 ms
yql
2545 ms
__utm.gif
33 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
84 ms
addthis_widget.js
83 ms
api.html
39 ms
sh.8e5f85691f9aaa082472a194.html
41 ms
moss.fm 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.
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.
moss.fm 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
moss.fm SEO score
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 Moss.fm 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 Moss.fm 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.
moss.fm
Open Graph data is detected on the main page of MOSS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: