Tools & Wizards About Us
e---e.me screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

e---e.me

Fun Pedia

Page Load Speed

2.1 sec in total

First Response

241 ms

Resources Loaded

1.7 sec

Page Rendered

131 ms

e---e.me screenshot

About Website

Visit e---e.me now to see the best up-to-date E content for Pakistan and also check out these interesting facts you probably never knew about e---e.me

Lols News is your best source of fun

Visit e---e.me

Key Findings

We analyzed E---e.me page load time and found that the first response time was 241 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

e---e.me performance score

0

Network Requests Diagram

e---e.me

241 ms

style.css

85 ms

menu.css

110 ms

jbar.css

110 ms

script.php

140 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 20% of them (22 requests) were addressed to the original E---e.me, 24% (27 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (851 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 183.3 kB (45%)

Content Size

403.2 kB

After Optimization

219.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E---e.me main page is 403.2 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. 80% 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. Javascripts take 165.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 76.8 kB

  • Original 98.7 kB
  • After minification 97.7 kB
  • After compression 22.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 76.8 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 4.3 kB

  • Original 128.5 kB
  • After minification 124.2 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. E images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 94.4 kB

  • Original 165.6 kB
  • After minification 165.1 kB
  • After compression 71.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 94.4 kB or 57% of the original size.

CSS Optimization

-75%

Potential reduce by 7.8 kB

  • Original 10.4 kB
  • After minification 9.5 kB
  • After compression 2.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. E---e.me needs all CSS files to be minified and compressed as it can save up to 7.8 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (68%)

Requests Now

100

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e---e.me

e---e.me

241 ms

style.css

style.css

85 ms

menu.css

menu.css

110 ms

jbar.css

jbar.css

110 ms

script.php

script.php

140 ms

jquery.min.js

jquery.min.js

290 ms

jquery.bar.js

jquery.bar.js

147 ms

plusone.js

plusone.js

70 ms

pinit.js

pinit.js

40 ms

all.js

all.js

8 ms

23 ms

PinExt.png

PinExt.png

16 ms

buttons.png

buttons.png

62 ms

5391c3eda7dda.jpg

5391c3eda7dda.jpg

143 ms

pixel.gif

pixel.gif

136 ms

feed.png

feed.png

64 ms

thumb_5391c3ed81ecd.jpg

thumb_5391c3ed81ecd.jpg

145 ms

thumb_53789a314da70.jpg

thumb_53789a314da70.jpg

139 ms

thumb_53552940e684e.jpg

thumb_53552940e684e.jpg

155 ms

thumb_539d836d550ad.jpg

thumb_539d836d550ad.jpg

213 ms

thumb_536f656173d48.jpg

thumb_536f656173d48.jpg

178 ms

thumb_539d8661bc2b0.jpg

thumb_539d8661bc2b0.jpg

239 ms

thumb_539d84a768bfd.jpg

thumb_539d84a768bfd.jpg

192 ms

thumb_53d8cdb81e559.jpg

thumb_53d8cdb81e559.jpg

210 ms

ga.js

ga.js

28 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

15 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

17 ms

fastbutton

fastbutton

106 ms

widgets.js

widgets.js

241 ms

small.js

small.js

152 ms

xd_arbiter.php

xd_arbiter.php

75 ms

xd_arbiter.php

xd_arbiter.php

115 ms

__utm.gif

__utm.gif

70 ms

postmessageRelay

postmessageRelay

81 ms

pinit_main.js

pinit_main.js

53 ms

comments.php

comments.php

851 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

45 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

42 ms

error

error

117 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

81 ms

like.php

like.php

159 ms

count.json

count.json

95 ms

share_button.php

share_button.php

149 ms

like_box.php

like_box.php

76 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

75 ms

rpc:shindig_random.js

rpc:shindig_random.js

47 ms

like.php

like.php

140 ms

36 ms

e---e.me

e---e.me

282 ms

dpx.js

dpx.js

8 ms

tpid=1EE70445D5F3ED5626039C36024463A2

tpid=1EE70445D5F3ED5626039C36024463A2

93 ms

p

p

55 ms

e---e.me

e---e.me

215 ms

hDvwL1_H7g-.css

hDvwL1_H7g-.css

89 ms

56WNbrUYLbL.css

56WNbrUYLbL.css

84 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

91 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

90 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

117 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

118 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

27 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

129 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

122 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

116 ms

dpx

dpx

31 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

100 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

98 ms

aol

aol

80 ms

12321119_191908171155616_6131987592362994561_n.png

12321119_191908171155616_6131987592362994561_n.png

81 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

52 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

51 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

23 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

25 ms

mapuser

mapuser

22 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

89 ms

51 ms

y_match

y_match

3 ms

match_redirect

match_redirect

5 ms

tc.js

tc.js

8 ms

29931

29931

28 ms

p

p

44 ms

match_redirect

match_redirect

4 ms

tpid=CE29559ED5F3ED56D36F2447029D1A48

tpid=CE29559ED5F3ED56D36F2447029D1A48

5 ms

lr

lr

4 ms

v2

v2

50 ms

dpx

dpx

3 ms

jot

jot

94 ms

ca.png

ca.png

167 ms

xrefid.xgi

xrefid.xgi

6 ms

lr.gif

lr.gif

10 ms

match_redirect

match_redirect

4 ms

sync

sync

15 ms

match_redirect

match_redirect

3 ms

CE29559ED5F3ED56D36F2447029D1A48

CE29559ED5F3ED56D36F2447029D1A48

35 ms

52154.gif

52154.gif

9 ms

match_redirect

match_redirect

4 ms

ProfilesEngineServlet

ProfilesEngineServlet

14 ms

ProfilesEngineServlet

ProfilesEngineServlet

341 ms

K4L53ZPHpV7.css

K4L53ZPHpV7.css

13 ms

xxJgcoj8mOR.css

xxJgcoj8mOR.css

18 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

34 ms

1FCa-btixu2.js

1FCa-btixu2.js

13 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

14 ms

FyxLoiww5bU.js

FyxLoiww5bU.js

14 ms

HaMjR2eXz4B.js

HaMjR2eXz4B.js

59 ms

WN2wSsLOuKy.js

WN2wSsLOuKy.js

58 ms

Kt4tkgSRvHH.js

Kt4tkgSRvHH.js

63 ms

Q4A0UyjU8W2.js

Q4A0UyjU8W2.js

54 ms

fav.png

fav.png

13 ms

odA9sNLrE86.jpg

odA9sNLrE86.jpg

5 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

8 ms

eR-qA8bp1RM.js

eR-qA8bp1RM.js

4 ms

tap.php

tap.php

6 ms

SEO Factors

e---e.me 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 E---e.me 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 E---e.me 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

e---e.me

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