Tools & Wizards About Us
wedding.screeninvasion.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wedding.screeninvasion.com

Geeky Wedding

Page Load Speed

8.8 sec in total

First Response

543 ms

Resources Loaded

2.9 sec

Page Rendered

5.4 sec

wedding.screeninvasion.com screenshot

About Website

Click here to check amazing Wedding Screeninvasion content for United States. Otherwise, check out these important facts you probably never knew about wedding.screeninvasion.com

I just had my own geeky wedding on June 30, 2012. I started this as a way to compile images, ideas, and thoughts during my wedding planning, but now it's just a fun collection of the girly and ge...

Visit wedding.screeninvasion.com

Key Findings

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

Performance Metrics

wedding.screeninvasion.com performance score

0

Network Requests Diagram

www.wedding.screeninvasion.com

543 ms

pre_tumblelog.js

13 ms

reset-min.css

19 ms

fonts.css

19 ms

jquery-1.4.2.min.js

20 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Wedding.screeninvasion.com, 25% (23 requests) were made to Static.tumblr.com and 17% (16 requests) were made to 40.media.tumblr.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source 36.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (10%)

Content Size

11.0 MB

After Optimization

9.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wedding.screeninvasion.com main page is 11.0 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. 85% 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 9.8 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 93.1 kB

  • Original 132.1 kB
  • After minification 126.2 kB
  • After compression 39.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. 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 93.1 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 326.4 kB

  • Original 9.8 MB
  • After minification 9.5 MB

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. Wedding Screeninvasion images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 504.6 kB

  • Original 793.3 kB
  • After minification 793.2 kB
  • After compression 288.7 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 504.6 kB or 64% of the original size.

CSS Optimization

-79%

Potential reduce by 208.1 kB

  • Original 263.2 kB
  • After minification 262.8 kB
  • After compression 55.1 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. Wedding.screeninvasion.com needs all CSS files to be minified and compressed as it can save up to 208.1 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

89

After Optimization

72

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wedding.screeninvasion.com

www.wedding.screeninvasion.com

543 ms

pre_tumblelog.js

pre_tumblelog.js

13 ms

reset-min.css

reset-min.css

19 ms

fonts.css

fonts.css

19 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

20 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

6 ms

stylesheet.css

stylesheet.css

7 ms

index.js

index.js

56 ms

ga.js

ga.js

140 ms

avatar_6bb83059d978_128.png

avatar_6bb83059d978_128.png

139 ms

tumblr_inline_o2f9ipspJv1tpra59_500.png

tumblr_inline_o2f9ipspJv1tpra59_500.png

360 ms

tumblr_inline_o2f9iwNSFe1tpra59_500.png

tumblr_inline_o2f9iwNSFe1tpra59_500.png

138 ms

tumblr_inline_o2f9j7AEqy1tpra59_500.png

tumblr_inline_o2f9j7AEqy1tpra59_500.png

327 ms

HZIxedCER9A

HZIxedCER9A

236 ms

false

false

169 ms

impixu

impixu

220 ms

tumblr_inline_nz4zshSvci1tpra59_500.png

tumblr_inline_nz4zshSvci1tpra59_500.png

374 ms

tumblr_inline_nygf12XWIi1tpra59_500.png

tumblr_inline_nygf12XWIi1tpra59_500.png

468 ms

tumblr_inline_nxzqypkFau1tpra59_500.png

tumblr_inline_nxzqypkFau1tpra59_500.png

472 ms

tumblr_inline_nxzqzcQT8s1tpra59_500.png

tumblr_inline_nxzqzcQT8s1tpra59_500.png

468 ms

tumblr_inline_nx0ttnv88Q1tpra59_500.png

tumblr_inline_nx0ttnv88Q1tpra59_500.png

372 ms

tumblr_inline_nx0tub01QR1tpra59_500.png

tumblr_inline_nx0tub01QR1tpra59_500.png

470 ms

tumblr_inline_nwlrckxGKD1tpra59_500.png

tumblr_inline_nwlrckxGKD1tpra59_500.png

521 ms

tumblr_inline_nvvwfgku5n1tpra59_500.png

tumblr_inline_nvvwfgku5n1tpra59_500.png

521 ms

tumblr_inline_nvvwfrweDY1tpra59_500.png

tumblr_inline_nvvwfrweDY1tpra59_500.png

487 ms

tumblr_inline_ntzwedR1LO1tpra59_500.png

tumblr_inline_ntzwedR1LO1tpra59_500.png

487 ms

tumblr_inline_ntzwf8mZCP1tpra59_500.png

tumblr_inline_ntzwf8mZCP1tpra59_500.png

485 ms

tumblr_inline_npq9jmqlYp1tpra59_500.png

tumblr_inline_npq9jmqlYp1tpra59_500.png

566 ms

tumblr_npg92tMZWV1qcs6gvo1_1280.jpg

tumblr_npg92tMZWV1qcs6gvo1_1280.jpg

551 ms

tumblr_inline_np9hec3BM61tpra59_500.png

tumblr_inline_np9hec3BM61tpra59_500.png

620 ms

tumblr_inline_nz4zsqUmzU1tpra59_500.png

tumblr_inline_nz4zsqUmzU1tpra59_500.png

465 ms

tumblr_inline_nygf1eSgwv1tpra59_500.png

tumblr_inline_nygf1eSgwv1tpra59_500.png

1311 ms

tumblr_inline_nx0ttzc8Kq1tpra59_500.png

tumblr_inline_nx0ttzc8Kq1tpra59_500.png

304 ms

tumblr_inline_nwlrcvag4p1tpra59_500.png

tumblr_inline_nwlrcvag4p1tpra59_500.png

282 ms

tumblr_inline_nwlrdbSTw31tpra59_500.png

tumblr_inline_nwlrdbSTw31tpra59_500.png

512 ms

tumblr_inline_np9hdymLuV1tpra59_500.png

tumblr_inline_np9hdymLuV1tpra59_500.png

2171 ms

tumblr_inline_np9hey6rVe1tpra59_500.png

tumblr_inline_np9hey6rVe1tpra59_500.png

563 ms

impixu

impixu

213 ms

bg.jpg

bg.jpg

134 ms

profilephotobg.jpg

profilephotobg.jpg

134 ms

archiveicon.jpg

archiveicon.jpg

135 ms

rssfeedicon.jpg

rssfeedicon.jpg

134 ms

askicon.jpg

askicon.jpg

135 ms

headerbg.png

headerbg.png

133 ms

infoicon.jpg

infoicon.jpg

136 ms

postdateicon.jpg

postdateicon.jpg

136 ms

likesicon.jpg

likesicon.jpg

136 ms

postbrake.jpg

postbrake.jpg

135 ms

caption-background.jpg

caption-background.jpg

136 ms

caption-background-ls.jpg

caption-background-ls.jpg

145 ms

caption-background-rs.jpg

caption-background-rs.jpg

152 ms

postfooterbg.jpg

postfooterbg.jpg

153 ms

postfooterls.jpg

postfooterls.jpg

152 ms

date-posted-icon.png

date-posted-icon.png

152 ms

notes-icon.png

notes-icon.png

142 ms

tagg-icon.png

tagg-icon.png

154 ms

postfooterrs.jpg

postfooterrs.jpg

155 ms

border-bottom.jpg

border-bottom.jpg

158 ms

tumblr_inline_nz4zrqwKrX1tpra59_500.png

tumblr_inline_nz4zrqwKrX1tpra59_500.png

142 ms

tumblr_inline_nygf0rRixD1tpra59_500.png

tumblr_inline_nygf0rRixD1tpra59_500.png

154 ms

tumblr_inline_nxzqz0aDgI1tpra59_500.png

tumblr_inline_nxzqz0aDgI1tpra59_500.png

154 ms

tumblr_inline_nvvwgb7VHE1tpra59_500.png

tumblr_inline_nvvwgb7VHE1tpra59_500.png

150 ms

tumblr_inline_nug9us340I1tpra59_500.png

tumblr_inline_nug9us340I1tpra59_500.png

150 ms

tumblr_inline_nug9v6Jbhe1tpra59_500.png

tumblr_inline_nug9v6Jbhe1tpra59_500.png

148 ms

tumblr_inline_nug9vjB8uu1tpra59_500.png

tumblr_inline_nug9vjB8uu1tpra59_500.png

161 ms

tumblr_inline_ntzweuqD8N1tpra59_500.png

tumblr_inline_ntzweuqD8N1tpra59_500.png

203 ms

tumblr_inline_nrvvjviFjX1tpra59_500.png

tumblr_inline_nrvvjviFjX1tpra59_500.png

203 ms

tumblr_inline_nrvvk6mULu1tpra59_500.png

tumblr_inline_nrvvk6mULu1tpra59_500.png

202 ms

tumblr_inline_nrvvkl8IzP1tpra59_500.png

tumblr_inline_nrvvkl8IzP1tpra59_500.png

159 ms

tumblr_inline_npq9kgeiIn1tpra59_540.png

tumblr_inline_npq9kgeiIn1tpra59_540.png

209 ms

tumblr_inline_npq9kwiEUe1tpra59_500.png

tumblr_inline_npq9kwiEUe1tpra59_500.png

201 ms

analytics.html

analytics.html

156 ms

2dg0t7I7FYGFOEAqmOfAuNGbhDRBgBHHiSMAAAA

2dg0t7I7FYGFOEAqmOfAuNGbhDRBgBHHiSMAAAA

31 ms

login_check.html

login_check.html

47 ms

__utm.gif

__utm.gif

32 ms

tumblr_npn432aaax1qg3bjuo2_250.jpg

tumblr_npn432aaax1qg3bjuo2_250.jpg

398 ms

tumblr_npn432aaax1qg3bjuo1_500.jpg

tumblr_npn432aaax1qg3bjuo1_500.jpg

59 ms

tumblr_npn432aaax1qg3bjuo3_250.jpg

tumblr_npn432aaax1qg3bjuo3_250.jpg

66 ms

rapid-3.36.js

rapid-3.36.js

55 ms

rapidworker-1.2.js

rapidworker-1.2.js

59 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

85 ms

www-embed-player.js

www-embed-player.js

99 ms

base.js

base.js

153 ms

ga.js

ga.js

54 ms

analytics.js

analytics.js

41 ms

cs.js

cs.js

51 ms

yql

yql

227 ms

__utm.gif

__utm.gif

40 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

51 ms

ad_status.js

ad_status.js

53 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

49 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

48 ms

cedexis.radar.js

cedexis.radar.js

4 ms

SEO Factors

wedding.screeninvasion.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

wedding.screeninvasion.com

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