Tools & Wizards About Us
simonandsarah.us screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

simonandsarah.us

Page Load Speed

2.6 sec in total

First Response

224 ms

Resources Loaded

2 sec

Page Rendered

409 ms

simonandsarah.us screenshot

About Website

Visit simonandsarah.us now to see the best up-to-date Simonandsarah content and also check out these interesting facts you probably never knew about simonandsarah.us

Visit simonandsarah.us

Key Findings

We analyzed Simonandsarah.us page load time and found that the first response time was 224 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

simonandsarah.us performance score

0

Network Requests Diagram

simonandsarah.us

224 ms

pre_tumblelog.js

14 ms

style.css

36 ms

modernizr-2.5.3.min.js

23 ms

jquery.min.js

33 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Simonandsarah.us, 15% (9 requests) were made to Apis.google.com and 15% (9 requests) were made to Static.tumblr.com. The less responsive or slowest element that took the longest time to load (666 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 473.1 kB (35%)

Content Size

1.3 MB

After Optimization

873.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Simonandsarah.us 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 617.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 36.5 kB

  • Original 47.5 kB
  • After minification 41.8 kB
  • After compression 11.0 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 5.8 kB, which is 12% 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 36.5 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 23.0 kB

  • Original 588.3 kB
  • After minification 565.3 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. Simonandsarah images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 366.2 kB

  • Original 617.2 kB
  • After minification 614.1 kB
  • After compression 251.0 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 366.2 kB or 59% of the original size.

CSS Optimization

-51%

Potential reduce by 47.4 kB

  • Original 93.3 kB
  • After minification 92.8 kB
  • After compression 45.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. Simonandsarah.us needs all CSS files to be minified and compressed as it can save up to 47.4 kB or 51% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (59%)

Requests Now

58

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Simonandsarah. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

simonandsarah.us

simonandsarah.us

224 ms

pre_tumblelog.js

pre_tumblelog.js

14 ms

style.css

style.css

36 ms

modernizr-2.5.3.min.js

modernizr-2.5.3.min.js

23 ms

jquery.min.js

jquery.min.js

33 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

18 ms

stylesheet.css

stylesheet.css

25 ms

css

css

104 ms

view.js

view.js

22 ms

script.js

script.js

24 ms

conversion.js

conversion.js

102 ms

index.js

index.js

28 ms

tumblr_inline_mt6lhgcVrW1ryhkp0.png

tumblr_inline_mt6lhgcVrW1ryhkp0.png

540 ms

tumblr_inline_mt6nvznzLD1ryhkp0.jpg

tumblr_inline_mt6nvznzLD1ryhkp0.jpg

597 ms

tumblr_inline_mt6o04nw291ryhkp0.jpg

tumblr_inline_mt6o04nw291ryhkp0.jpg

290 ms

tumblr_inline_mt6o0yihgt1ryhkp0.jpg

tumblr_inline_mt6o0yihgt1ryhkp0.jpg

297 ms

tumblr_static_aisle.jpg

tumblr_static_aisle.jpg

587 ms

share-plus.png

share-plus.png

274 ms

pxu_logo.png

pxu_logo.png

275 ms

social-icons.png

social-icons.png

274 ms

plusone.js

plusone.js

570 ms

all.js

all.js

666 ms

impixu

impixu

651 ms

widgets.js

widgets.js

280 ms

impixu

impixu

416 ms

search.png

search.png

28 ms

analytics.html

analytics.html

413 ms

login_check.html

login_check.html

27 ms

kteN-TiU7KwgPz3aaBeTSQ.ttf

kteN-TiU7KwgPz3aaBeTSQ.ttf

312 ms

avatar_a66889c8e14f_40.png

avatar_a66889c8e14f_40.png

166 ms

iframe_logo.png

iframe_logo.png

247 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

242 ms

like.php

like.php

268 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

141 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

229 ms

fastbutton

fastbutton

312 ms

like.php

like.php

262 ms

rapid-3.36.js

rapid-3.36.js

276 ms

rapidworker-1.2.js

rapidworker-1.2.js

282 ms

183 ms

xd_arbiter.php

xd_arbiter.php

349 ms

xd_arbiter.php

xd_arbiter.php

559 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

632 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

511 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

57 ms

postmessageRelay

postmessageRelay

213 ms

rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw

rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw

55 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

591 ms

ga.js

ga.js

170 ms

analytics.js

analytics.js

229 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

87 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

85 ms

cs.js

cs.js

266 ms

yql

yql

341 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

224 ms

rpc:shindig_random.js

rpc:shindig_random.js

110 ms

__utm.gif

__utm.gif

74 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

115 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

12 ms

jot.html

jot.html

24 ms

cedexis.radar.js

cedexis.radar.js

13 ms

SEO Factors

simonandsarah.us 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 Simonandsarah.us 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 Simonandsarah.us 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

simonandsarah.us

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