Tools & Wizards About Us
phunkyphresh.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

phunkyphresh.com

Phunky Phresh

Page Load Speed

3.8 sec in total

First Response

206 ms

Resources Loaded

3.3 sec

Page Rendered

224 ms

phunkyphresh.com screenshot

About Website

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

Phunky Phresh clothing

Visit phunkyphresh.com

Key Findings

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

Performance Metrics

phunkyphresh.com performance score

0

Network Requests Diagram

phunkyphresh.com

206 ms

ga.js

6 ms

home.css

47 ms

show_news.php

583 ms

show_ads.js

35 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 25% of them (21 requests) were addressed to the original Phunkyphresh.com, 8% (7 requests) were made to Static.xx.fbcdn.net and 7% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Fastonlineusers.com.

Page Optimization Overview & Recommendations

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

Content Size

2.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phunkyphresh.com main page is 2.1 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 109.8 kB

  • Original 138.9 kB
  • After minification 138.2 kB
  • After compression 29.1 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 109.8 kB or 79% of the original size.

Image Optimization

-13%

Potential reduce by 85.6 kB

  • Original 652.8 kB
  • After minification 567.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. Obviously, Phunky Phresh needs image optimization as it can save up to 85.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 842.2 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 480.8 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 842.2 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 29.7 kB

  • Original 35.1 kB
  • After minification 32.0 kB
  • After compression 5.4 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. Phunkyphresh.com needs all CSS files to be minified and compressed as it can save up to 29.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (56%)

Requests Now

79

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phunkyphresh.com

phunkyphresh.com

206 ms

ga.js

ga.js

6 ms

home.css

home.css

47 ms

show_news.php

show_news.php

583 ms

show_ads.js

show_ads.js

35 ms

qb-ban-ani.gif

qb-ban-ani.gif

218 ms

pinit.js

pinit.js

88 ms

top2011.png

top2011.png

190 ms

new.gif

new.gif

86 ms

__utm.gif

__utm.gif

53 ms

counter.js

counter.js

55 ms

i.gif

i.gif

6 ms

banners

banners

155 ms

addthis_widget.js

addthis_widget.js

50 ms

ca-pub-2770139313865709.js

ca-pub-2770139313865709.js

59 ms

zrt_lookup.html

zrt_lookup.html

41 ms

show_ads_impl.js

show_ads_impl.js

53 ms

301 ms

220 ms

backgroundb.png

backgroundb.png

100 ms

h1b.png

h1b.png

109 ms

h5.png

h5.png

99 ms

h1.png

h1.png

107 ms

nav.png

nav.png

108 ms

h3.png

h3.png

108 ms

pinit_main.js

pinit_main.js

3 ms

ads

ads

193 ms

osd.js

osd.js

13 ms

likebox.php

likebox.php

350 ms

banners

banners

108 ms

ads

ads

148 ms

ads

ads

140 ms

ads

ads

197 ms

88 ms

snd2.png

snd2.png

20 ms

jsc_1502443193.js

jsc_1502443193.js

33 ms

abg.js

abg.js

70 ms

osd_listener.js

osd_listener.js

78 ms

01.png

01.png

65 ms

YrFakaCOmcf.css

YrFakaCOmcf.css

22 ms

twctMluLnG3.js

twctMluLnG3.js

29 ms

JrFVMrRpAYB.js

JrFVMrRpAYB.js

58 ms

T-D_V7C7Ph6.js

T-D_V7C7Ph6.js

57 ms

10996228_903277463050367_7064751471893172362_n.png

10996228_903277463050367_7064751471893172362_n.png

111 ms

37653_127149893996465_5026448_n.jpg

37653_127149893996465_5026448_n.jpg

24 ms

16143158_10212647219162242_1848434065959439137_n.jpg

16143158_10212647219162242_1848434065959439137_n.jpg

25 ms

20799046_1789249897771164_3832150312026809188_n.jpg

20799046_1789249897771164_3832150312026809188_n.jpg

52 ms

14522736_10205211824374235_4391735115751644893_n.jpg

14522736_10205211824374235_4391735115751644893_n.jpg

90 ms

wMkwmq5_RAN.png

wMkwmq5_RAN.png

8 ms

home.css

home.css

31 ms

twitter.png

twitter.png

25 ms

02.png

02.png

47 ms

14.png

14.png

46 ms

11.png

11.png

65 ms

pinit_main.js

pinit_main.js

4 ms

none

none

31 ms

home.css

home.css

22 ms

e2ffa70ceed631c961c780c3bca3349d

e2ffa70ceed631c961c780c3bca3349d

38 ms

pksizxtp.f.kk[0]

pksizxtp.f.kk[0]

43 ms

on3.php

on3.php

1012 ms

activeview

activeview

13 ms

text.php

text.php

151 ms

s11.g

s11.g

1003 ms

h4.png

h4.png

39 ms

ads

ads

113 ms

nav3.png

nav3.png

64 ms

ui_tag_3.70-37.1.js

ui_tag_3.70-37.1.js

52 ms

like.php

like.php

76 ms

_ate.track.config_resp

_ate.track.config_resp

57 ms

300lo.json

300lo.json

61 ms

it-ui-comp-120x600.css

it-ui-comp-120x600.css

11 ms

sh.48536d49e4da3bdba54606b4.html

sh.48536d49e4da3bdba54606b4.html

41 ms

17s4-Xv6HwR.js

17s4-Xv6HwR.js

24 ms

lH1ibRl5GKq.png

lH1ibRl5GKq.png

21 ms

findBanner

findBanner

43 ms

counter.e61152ce165bc90fac45.js

counter.e61152ce165bc90fac45.js

13 ms

it-banner-frame.css

it-banner-frame.css

7 ms

112 ms

shares.json

shares.json

20 ms

107 ms

pixel

pixel

14 ms

pixel

pixel

13 ms

match-result

match-result

3 ms

match-result

match-result

3 ms

e2ffa70ceed631c961c780c3bca3349d

e2ffa70ceed631c961c780c3bca3349d

14 ms

SEO Factors

phunkyphresh.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phunkyphresh.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 Phunkyphresh.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

phunkyphresh.com

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