Tools & Wizards About Us
us.fm screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

us.fm

Webmasters.com | Cheap Domains, Web Hosting, Servers & Website Design

Page Load Speed

1.5 sec in total

First Response

171 ms

Resources Loaded

967 ms

Page Rendered

342 ms

us.fm screenshot

About Website

Click here to check amazing Us content for Israel. Otherwise, check out these important facts you probably never knew about us.fm

$9.95/month business hosting, PHP web hosting, PHP hosting, PHP MySQL hosting, domain registration, ecommerce, webhosting with SSL, Perl, website design.

Visit us.fm

Key Findings

We analyzed Us.fm page load time and found that the first response time was 171 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

us.fm performance score

0

Network Requests Diagram

us.fm

171 ms

style.css

69 ms

rollover.js

83 ms

jquery-1.2.3.min.js

223 ms

jquery.flow.1.0.js

84 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 96% of them (76 requests) were addressed to the original Us.fm, 1% (1 request) were made to Sitechat.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (484 ms) relates to the external source Sitechat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.2 kB (25%)

Content Size

447.6 kB

After Optimization

336.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Us.fm main page is 447.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 308.0 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 45.6 kB

  • Original 53.7 kB
  • After minification 52.1 kB
  • After compression 8.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 45.6 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 294 B

  • Original 308.0 kB
  • After minification 307.7 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. Us images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 41.5 kB

  • Original 58.7 kB
  • After minification 57.6 kB
  • After compression 17.2 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 41.5 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 23.8 kB

  • Original 27.3 kB
  • After minification 23.9 kB
  • After compression 3.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. Us.fm needs all CSS files to be minified and compressed as it can save up to 23.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (25%)

Requests Now

75

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Us. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

us.fm

us.fm

171 ms

style.css

style.css

69 ms

rollover.js

rollover.js

83 ms

jquery-1.2.3.min.js

jquery-1.2.3.min.js

223 ms

jquery.flow.1.0.js

jquery.flow.1.0.js

84 ms

script.php

script.php

484 ms

bg.gif

bg.gif

43 ms

logo.gif

logo.gif

37 ms

top_bg.gif

top_bg.gif

40 ms

arrow2a.gif

arrow2a.gif

40 ms

arrow2.gif

arrow2.gif

37 ms

arow3.gif

arow3.gif

69 ms

free_support.gif

free_support.gif

75 ms

mainnav_btnup.gif

mainnav_btnup.gif

69 ms

mainnav_btn.gif

mainnav_btn.gif

70 ms

body_bg2.gif

body_bg2.gif

72 ms

body_bg1.gif

body_bg1.gif

74 ms

banner_green.gif

banner_green.gif

235 ms

doamin_banner.gif

doamin_banner.gif

203 ms

arrow8.png

arrow8.png

103 ms

blank.gif

blank.gif

105 ms

webhosting_banner.jpg

webhosting_banner.jpg

172 ms

servers_banner.jpg

servers_banner.jpg

176 ms

webdesign_banner.jpg

webdesign_banner.jpg

312 ms

ecommerce_banner.jpg

ecommerce_banner.jpg

312 ms

traffic_banner.jpg

traffic_banner.jpg

240 ms

domains_btn.gif

domains_btn.gif

210 ms

domains_btnup.gif

domains_btnup.gif

235 ms

webhost_btn.gif

webhost_btn.gif

245 ms

webhost_btnup.gif

webhost_btnup.gif

310 ms

servers_btn.gif

servers_btn.gif

312 ms

servers_btnup.gif

servers_btnup.gif

312 ms

webdesign_btn.gif

webdesign_btn.gif

313 ms

webdesign_btnup.gif

webdesign_btnup.gif

318 ms

ecommerce_btn.gif

ecommerce_btn.gif

316 ms

ecommerce_btnup.gif

ecommerce_btnup.gif

317 ms

build_btn.gif

build_btn.gif

316 ms

build_btnup.gif

build_btnup.gif

317 ms

green_tab.png

green_tab.png

318 ms

footer_bg.gif

footer_bg.gif

348 ms

leftbox_top.gif

leftbox_top.gif

348 ms

left_top_rotatebg.gif

left_top_rotatebg.gif

324 ms

left_top_stopbg.gif

left_top_stopbg.gif

324 ms

more.gif

more.gif

323 ms

leftbox_btm.gif

leftbox_btm.gif

323 ms

left_box1.gif

left_box1.gif

351 ms

start_yours.gif

start_yours.gif

354 ms

left_box2_bg2.gif

left_box2_bg2.gif

326 ms

left_box2_bg1.gif

left_box2_bg1.gif

330 ms

left_box2_btm.gif

left_box2_btm.gif

332 ms

left_box3.gif

left_box3.gif

331 ms

moneyback.gif

moneyback.gif

355 ms

arrow3.gif

arrow3.gif

354 ms

control_panel_icon.gif

control_panel_icon.gif

334 ms

arrow6.gif

arrow6.gif

334 ms

border.gif

border.gif

269 ms

topten_icon.gif

topten_icon.gif

261 ms

testimonial_icon.gif

testimonial_icon.gif

254 ms

ordernow_icon.gif

ordernow_icon.gif

246 ms

arrow7.gif

arrow7.gif

226 ms

right_top.gif

right_top.gif

228 ms

right_bg.jpg

right_bg.jpg

227 ms

box1.gif

box1.gif

236 ms

css

css

79 ms

get_started.gif

get_started.gif

178 ms

box2.gif

box2.gif

179 ms

text1.gif

text1.gif

181 ms

box3.gif

box3.gif

185 ms

details.gif

details.gif

187 ms

box4.gif

box4.gif

202 ms

find_btn.gif

find_btn.gif

206 ms

right_btm.gif

right_btm.gif

206 ms

emailpage.gif

emailpage.gif

208 ms

bookmark.gif

bookmark.gif

214 ms

sub_navbg.gif

sub_navbg.gif

214 ms

footer_curve.gif

footer_curve.gif

227 ms

mUangSEE-PUZJVLGz-Lt6-vvDin1pK8aKteLpeZ5c0A.ttf

mUangSEE-PUZJVLGz-Lt6-vvDin1pK8aKteLpeZ5c0A.ttf

71 ms

domaining-120x31.gif

domaining-120x31.gif

206 ms

footer_logo.gif

footer_logo.gif

207 ms

SEO Factors

us.fm SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Us.fm 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Us.fm main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

us.fm

Open Graph description is not detected on the main page of Us. 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: