Tools & Wizards About Us
edwardmarks.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

edwardmarks.com

Tumblr

Page Load Speed

3 sec in total

First Response

330 ms

Resources Loaded

815 ms

Page Rendered

1.8 sec

edwardmarks.com screenshot

About Website

Welcome to edwardmarks.com homepage info - get ready to check Edwardmarks best content right away, or after learning these important things about edwardmarks.com

Tumblr. Pure effervescent enrichment. Old internet energy. Home of the Reblogs. All the art you never knew you needed. All the fandoms you could wish for. Enough memes to knock out a moderately-sized ...

Visit edwardmarks.com

Key Findings

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

Performance Metrics

edwardmarks.com performance score

0

Network Requests Diagram

blog.edwardmarks.com

330 ms

pre_tumblelog.js

5 ms

tumblelog_post_message_queue.js

9 ms

stylesheet.css

8 ms

widgets.js

154 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Edwardmarks.com, 21% (8 requests) were made to Assets.tumblr.com and 11% (4 requests) were made to 33.media.tumblr.com. The less responsive or slowest element that took the longest time to load (330 ms) relates to the external source Blog.edwardmarks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 417.9 kB (34%)

Content Size

1.2 MB

After Optimization

800.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Edwardmarks.com main page is 1.2 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. 55% of websites need less resources to load. Images take 651.8 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 38.7 kB

  • Original 57.4 kB
  • After minification 56.0 kB
  • After compression 18.7 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 38.7 kB or 67% of the original size.

Image Optimization

-9%

Potential reduce by 59.7 kB

  • Original 651.8 kB
  • After minification 592.1 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. Edwardmarks images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 319.2 kB

  • Original 508.4 kB
  • After minification 508.4 kB
  • After compression 189.3 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 319.2 kB or 63% of the original size.

CSS Optimization

-59%

Potential reduce by 384 B

  • Original 655 B
  • After minification 655 B
  • After compression 271 B

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. Edwardmarks.com needs all CSS files to be minified and compressed as it can save up to 384 B or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (30%)

Requests Now

37

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.edwardmarks.com

blog.edwardmarks.com

330 ms

pre_tumblelog.js

pre_tumblelog.js

5 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

9 ms

stylesheet.css

stylesheet.css

8 ms

widgets.js

widgets.js

154 ms

tumblr_inline_mtepss29T71qhi96o.png

tumblr_inline_mtepss29T71qhi96o.png

180 ms

tumblr_m9uzg6WsHJ1qhi96o.png

tumblr_m9uzg6WsHJ1qhi96o.png

25 ms

tumblr_m9uzgoCI4q1qhi96o.png

tumblr_m9uzgoCI4q1qhi96o.png

142 ms

tumblr_m9uzhp3OcV1qhi96o.png

tumblr_m9uzhp3OcV1qhi96o.png

23 ms

tumblr_m9uzygqOgz1qhi96o.png

tumblr_m9uzygqOgz1qhi96o.png

24 ms

tumblr_m8o69edbAu1qhi96o.png

tumblr_m8o69edbAu1qhi96o.png

24 ms

tumblr_inline_mtfvdutJWt1qhi96o.png

tumblr_inline_mtfvdutJWt1qhi96o.png

203 ms

tumblr_m9uzfubMfE1qhi96o.png

tumblr_m9uzfubMfE1qhi96o.png

246 ms

tumblr_m9uzsphs661qhi96o.png

tumblr_m9uzsphs661qhi96o.png

265 ms

tumblr_m8o66nvIN81qhi96o.png

tumblr_m8o66nvIN81qhi96o.png

244 ms

tumblr_m8o67bu2C51qhi96o.png

tumblr_m8o67bu2C51qhi96o.png

244 ms

tumblr_m8yrc60Z2a1qhi96o.png

tumblr_m8yrc60Z2a1qhi96o.png

268 ms

tumblr_m8yrcmTPun1qhi96o.png

tumblr_m8yrcmTPun1qhi96o.png

265 ms

tumblr_m8o7giFwNk1qhi96o.png

tumblr_m8o7giFwNk1qhi96o.png

304 ms

tumblr_m9uzsw5yQ91qhi96o.png

tumblr_m9uzsw5yQ91qhi96o.png

137 ms

ga.js

ga.js

20 ms

impixu

impixu

189 ms

index.js

index.js

53 ms

tumblr_m8o6a1YyR41qhi96o.png

tumblr_m8o6a1YyR41qhi96o.png

291 ms

impixu

impixu

209 ms

analytics.html

analytics.html

156 ms

__utm.gif

__utm.gif

106 ms

login_check.html

login_check.html

36 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

165 ms

rapid-3.36.js

rapid-3.36.js

62 ms

rapidworker-1.2.js

rapidworker-1.2.js

61 ms

ga.js

ga.js

39 ms

analytics.js

analytics.js

66 ms

cs.js

cs.js

77 ms

__utm.gif

__utm.gif

23 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

53 ms

__utm.gif

__utm.gif

5 ms

cedexis.radar.js

cedexis.radar.js

4 ms

SEO Factors

edwardmarks.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edwardmarks.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Edwardmarks.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

edwardmarks.com

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