Tools & Wizards About Us
phorum.gr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

phorum.gr

phorum.gr

Page Load Speed

4.2 sec in total

First Response

470 ms

Resources Loaded

3.4 sec

Page Rendered

246 ms

phorum.gr screenshot

About Website

Visit phorum.gr now to see the best up-to-date Phorum content for Greece and also check out these interesting facts you probably never knew about phorum.gr

Visit phorum.gr

Key Findings

We analyzed Phorum.gr page load time and found that the first response time was 470 ms and then it took 3.7 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

phorum.gr performance score

0

Network Requests Diagram

phorum.gr

470 ms

www.phorum.gr

653 ms

styleswitcher.js

183 ms

forum_fn.js

180 ms

jquery.min.js

751 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 40% of them (26 requests) were addressed to the original Phorum.gr, 15% (10 requests) were made to Static.xx.fbcdn.net and 11% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (751 ms) belongs to the original domain Phorum.gr.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.4 kB (53%)

Content Size

355.0 kB

After Optimization

168.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phorum.gr main page is 355.0 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. 45% of websites need less resources to load. Javascripts take 194.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 63.9 kB

  • Original 75.9 kB
  • After minification 64.3 kB
  • After compression 12.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 11.6 kB, which is 15% 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 63.9 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 6.6 kB

  • Original 70.2 kB
  • After minification 63.6 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. Phorum images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 105.1 kB

  • Original 194.9 kB
  • After minification 186.0 kB
  • After compression 89.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 105.1 kB or 54% of the original size.

CSS Optimization

-77%

Potential reduce by 10.8 kB

  • Original 14.0 kB
  • After minification 11.2 kB
  • After compression 3.2 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. Phorum.gr needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (80%)

Requests Now

60

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phorum.gr

phorum.gr

470 ms

www.phorum.gr

www.phorum.gr

653 ms

styleswitcher.js

styleswitcher.js

183 ms

forum_fn.js

forum_fn.js

180 ms

jquery.min.js

jquery.min.js

751 ms

reimg.js

reimg.js

180 ms

litebox.js

litebox.js

183 ms

style.php

style.php

381 ms

normal.css

normal.css

268 ms

rating.css

rating.css

269 ms

show_ads.js

show_ads.js

5 ms

b

b

7 ms

corners_left.png

corners_left.png

142 ms

corners_right.png

corners_right.png

141 ms

site_logo.gif

site_logo.gif

282 ms

icon_home.gif

icon_home.gif

140 ms

icon_fontsize.gif

icon_fontsize.gif

141 ms

icon_faq.gif

icon_faq.gif

141 ms

icon_register.gif

icon_register.gif

180 ms

icon_logout.gif

icon_logout.gif

181 ms

gradient.gif

gradient.gif

180 ms

forum_read.gif

forum_read.gif

180 ms

icon_topic_latest.gif

icon_topic_latest.gif

184 ms

tb_26_16072012.jpg

tb_26_16072012.jpg

447 ms

bsa.js

bsa.js

26 ms

bg_button.gif

bg_button.gif

263 ms

ca-pub-3562870139855556.js

ca-pub-3562870139855556.js

143 ms

zrt_lookup.html

zrt_lookup.html

28 ms

show_ads_impl.js

show_ads_impl.js

80 ms

plusone.js

plusone.js

104 ms

s.gif

s.gif

16 ms

ga.js

ga.js

34 ms

s_0d2566f7911a4c4ba1f170b6b36fccd7.js

s_0d2566f7911a4c4ba1f170b6b36fccd7.js

129 ms

__utm.gif

__utm.gif

59 ms

ads

ads

29 ms

osd.js

osd.js

21 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

88 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

108 ms

fastbutton

fastbutton

178 ms

likebox.php

likebox.php

194 ms

collect

collect

78 ms

pro.js

pro.js

2 ms

438 ms

postmessageRelay

postmessageRelay

35 ms

api.js

api.js

51 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

78 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

67 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

24 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

38 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

92 ms

xYm_UD1pmAz.css

xYm_UD1pmAz.css

288 ms

TGpOWuX6Pv8.css

TGpOWuX6Pv8.css

355 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

490 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

620 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

509 ms

TTCre3391I0.js

TTCre3391I0.js

509 ms

print.css

print.css

93 ms

medium.css

medium.css

94 ms

large.css

large.css

93 ms

431288_278639638873108_895364088_n.jpg

431288_278639638873108_895364088_n.jpg

419 ms

644738_441280735942330_1919566555_n.jpg

644738_441280735942330_1919566555_n.jpg

484 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

73 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

73 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

68 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

135 ms

SEO Factors

phorum.gr SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phorum.gr 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 Greek. Our system also found out that Phorum.gr 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

phorum.gr

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