Tools & Wizards About Us
socialmemos.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

socialmemos.com

Page Load Speed

3.6 sec in total

First Response

605 ms

Resources Loaded

2.7 sec

Page Rendered

326 ms

socialmemos.com screenshot

About Website

Click here to check amazing Socialmemos content for Indonesia. Otherwise, check out these important facts you probably never knew about socialmemos.com

Michal Sadowski - Founder at Brand24 Blogger, Public Speaker and Social Media Enthusiast

Visit socialmemos.com

Key Findings

We analyzed Socialmemos.com page load time and found that the first response time was 605 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

socialmemos.com performance score

0

Network Requests Diagram

socialmemos.com

605 ms

style.css

147 ms

light.css

237 ms

jquery.fancybox-1.3.4.css

262 ms

jquery.min.js

55 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 44% of them (30 requests) were addressed to the original Socialmemos.com, 6% (4 requests) were made to F.vimeocdn.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (933 ms) belongs to the original domain Socialmemos.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (66%)

Content Size

1.6 MB

After Optimization

534.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Socialmemos.com main page is 1.6 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 917.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 39.6 kB

  • Original 49.1 kB
  • After minification 38.5 kB
  • After compression 9.5 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 10.6 kB, which is 22% 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 39.6 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 18.9 kB

  • Original 194.6 kB
  • After minification 175.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. Socialmemos images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 631.5 kB

  • Original 917.6 kB
  • After minification 901.4 kB
  • After compression 286.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 631.5 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 349.0 kB

  • Original 412.2 kB
  • After minification 399.3 kB
  • After compression 63.2 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. Socialmemos.com needs all CSS files to be minified and compressed as it can save up to 349.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (60%)

Requests Now

63

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

socialmemos.com

socialmemos.com

605 ms

style.css

style.css

147 ms

light.css

light.css

237 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

262 ms

jquery.min.js

jquery.min.js

55 ms

jquery-ui-1.8.5.custom.min.js

jquery-ui-1.8.5.custom.min.js

482 ms

jquery.shortcodes.js

jquery.shortcodes.js

284 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

284 ms

slides.min.jquery.js

slides.min.jquery.js

284 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

352 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

352 ms

follow

follow

10 ms

jquery.custom.js

jquery.custom.js

371 ms

comment-reply.min.js

comment-reply.min.js

373 ms

masonry.min.js

masonry.min.js

397 ms

wp-embed.min.js

wp-embed.min.js

468 ms

follow

follow

88 ms

-widgets.jsedf623d30ddc52b6.js

-widgets.jsedf623d30ddc52b6.js

25 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

220 ms

body_bg.gif

body_bg.gif

338 ms

logo-exp.png

logo-exp.png

337 ms

fb_1.png

fb_1.png

336 ms

twitter_1.png

twitter_1.png

337 ms

google_plus.png

google_plus.png

338 ms

linkedin.png

linkedin.png

337 ms

klout.png

klout.png

464 ms

thank-you1-360x250.jpg

thank-you1-360x250.jpg

651 ms

FireShot-Screen-Capture-264-The-Peoples-Stage-Final-I-Web-Summit-October-30-31-2013-www_websummit_net_competitions_peoples-stage_entries_html-360x128.png

FireShot-Screen-Capture-264-The-Peoples-Stage-Final-I-Web-Summit-October-30-31-2013-www_websummit_net_competitions_peoples-stage_entries_html-360x128.png

933 ms

front-360x202.jpg

front-360x202.jpg

650 ms

3v3j27-360x202.jpg

3v3j27-360x202.jpg

667 ms

886355_163154937175107_1219737189_o-360x223.jpg

886355_163154937175107_1219737189_o-360x223.jpg

825 ms

fb-api-360x203.jpg

fb-api-360x203.jpg

649 ms

all.js

all.js

383 ms

widgets.js

widgets.js

12 ms

116533351

116533351

314 ms

sprite.png

sprite.png

801 ms

overlay.png

overlay.png

801 ms

ga.js

ga.js

33 ms

count.js

count.js

401 ms

3wjHPEGmP-A

3wjHPEGmP-A

312 ms

y2Qi2PcGPiw

y2Qi2PcGPiw

399 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

62 ms

__utm.gif

__utm.gif

61 ms

player.js

player.js

188 ms

player.css

player.css

150 ms

ga.js

ga.js

133 ms

vuid.min.js

vuid.min.js

156 ms

subscribe.php

subscribe.php

315 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

81 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

126 ms

www-embed-player.js

www-embed-player.js

230 ms

base.js

base.js

294 ms

info.json

info.json

381 ms

368 ms

xd_arbiter.php

xd_arbiter.php

362 ms

xd_arbiter.php

xd_arbiter.php

634 ms

__utm.gif

__utm.gif

42 ms

proxy.html

proxy.html

91 ms

502919635.jpg

502919635.jpg

363 ms

8950371_60x60.jpg

8950371_60x60.jpg

226 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

626 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

705 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

93 ms

ad_status.js

ad_status.js

94 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

54 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

61 ms

jot

jot

91 ms

xd_arbiter.php

xd_arbiter.php

139 ms

SEO Factors

socialmemos.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Socialmemos.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 Socialmemos.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.

Social Sharing Optimization

socialmemos.com

Open Graph data is detected on the main page of Socialmemos. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: