Tools & Wizards About Us
cmfr-phil.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cmfr-phil.org

CMFR |

Page Load Speed

15 sec in total

First Response

6.1 sec

Resources Loaded

7.9 sec

Page Rendered

964 ms

cmfr-phil.org screenshot

About Website

Visit cmfr-phil.org now to see the best up-to-date CMFR Phil content for Philippines and also check out these interesting facts you probably never knew about cmfr-phil.org

A TIMELY question a year after the "Battle for Manila Bay" was launched: Who's winning?

Visit cmfr-phil.org

Key Findings

We analyzed Cmfr-phil.org page load time and found that the first response time was 6.1 sec and then it took 8.9 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

cmfr-phil.org performance score

0

Network Requests Diagram

cmfr-phil.org

6098 ms

wp-emoji-release.min.js

32 ms

default-style.css

30 ms

foobox.free.min.css

80 ms

bootstrap.min.css

92 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 66% of them (67 requests) were addressed to the original Cmfr-phil.org, 8% (8 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Cmfr-phil.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (6%)

Content Size

17.3 MB

After Optimization

16.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cmfr-phil.org main page is 17.3 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. 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. Images take 16.0 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 178.6 kB

  • Original 201.7 kB
  • After minification 143.7 kB
  • After compression 23.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. This page needs HTML code to be minified as it can gain 57.9 kB, which is 29% 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 178.6 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 91.3 kB

  • Original 16.0 MB
  • After minification 15.9 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. CMFR Phil images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 370.8 kB

  • Original 558.1 kB
  • After minification 552.0 kB
  • After compression 187.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 370.8 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 408.8 kB

  • Original 492.4 kB
  • After minification 471.9 kB
  • After compression 83.6 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. Cmfr-phil.org needs all CSS files to be minified and compressed as it can save up to 408.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (55%)

Requests Now

93

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cmfr-phil.org

cmfr-phil.org

6098 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

32 ms

default-style.css

default-style.css

30 ms

foobox.free.min.css

foobox.free.min.css

80 ms

bootstrap.min.css

bootstrap.min.css

92 ms

blueimp-gallery.min.css

blueimp-gallery.min.css

32 ms

font-awesome.min.css

font-awesome.min.css

57 ms

style.css

style.css

75 ms

animations.css

animations.css

74 ms

upw-theme-standard.min.css

upw-theme-standard.min.css

78 ms

styles.css

styles.css

97 ms

magnific-popup.css

magnific-popup.css

85 ms

awp-columns.css

awp-columns.css

86 ms

shortcodes.css

shortcodes.css

94 ms

style_2.1.2.css

style_2.1.2.css

97 ms

jquery.js

jquery.js

120 ms

jquery-migrate.min.js

jquery-migrate.min.js

104 ms

bootstrap.min.js

bootstrap.min.js

104 ms

jquery.blueimp-gallery.min.js

jquery.blueimp-gallery.min.js

103 ms

bootstrap-image-gallery.min.js

bootstrap-image-gallery.min.js

103 ms

jquery.bcSwipe.min.js

jquery.bcSwipe.min.js

102 ms

scripts.js

scripts.js

155 ms

foobox.free.min.js

foobox.free.min.js

164 ms

script_2.1.2.js

script_2.1.2.js

156 ms

button.facebook.js

button.facebook.js

155 ms

all.js

all.js

20 ms

button.googleplus.js

button.googleplus.js

151 ms

in.js

in.js

7 ms

widgets.js

widgets.js

212 ms

css

css

90 ms

css

css

106 ms

ninja-forms-display.css

ninja-forms-display.css

98 ms

qtip.css

qtip.css

201 ms

jquery.rating.css

jquery.rating.css

198 ms

baw-script.min.js

baw-script.min.js

156 ms

player_api

player_api

89 ms

scripts.js

scripts.js

200 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

199 ms

jquery.form.min.js

jquery.form.min.js

202 ms

underscore.min.js

underscore.min.js

204 ms

backbone.min.js

backbone.min.js

232 ms

ninja-forms-display.min.js

ninja-forms-display.min.js

233 ms

count.js

count.js

203 ms

plusone.js

plusone.js

110 ms

secureAnonymousFramework

secureAnonymousFramework

129 ms

424 ms

cmfr-logo.jpg

cmfr-logo.jpg

82 ms

EDSA_slider2.png

EDSA_slider2.png

820 ms

duterte.png

duterte.png

1263 ms

Journalism-Review_Thumbnail-for-SLIDER.png

Journalism-Review_Thumbnail-for-SLIDER.png

289 ms

rh.png

rh.png

1609 ms

bblprotest.png

bblprotest.png

1395 ms

img-placeholder.jpg

img-placeholder.jpg

408 ms

test3-150x150.png

test3-150x150.png

407 ms

test2-150x150.png

test2-150x150.png

467 ms

FINAL-Absent-from-EDSA-MDJ_PHOTO-150x150.jpg

FINAL-Absent-from-EDSA-MDJ_PHOTO-150x150.jpg

467 ms

MediaXPeace2015_Sidebar.png

MediaXPeace2015_Sidebar.png

518 ms

Media-Times-Sidebar.png

Media-Times-Sidebar.png

517 ms

FOI-SIDE.jpg

FOI-SIDE.jpg

550 ms

PAGE_sidebar.jpg

PAGE_sidebar.jpg

550 ms

Cybercrime-Sidebar.jpg

Cybercrime-Sidebar.jpg

636 ms

Martial-Law-Sidebar.png

Martial-Law-Sidebar.png

635 ms

CMFR_FINAL_White-Text.png

CMFR_FINAL_White-Text.png

637 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

340 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

368 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

363 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

421 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

742 ms

Picture-352.jpg

Picture-352.jpg

733 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

352 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

406 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

406 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

408 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

730 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

440 ms

100_3687.jpg

100_3687.jpg

712 ms

NUJP-oath-taking.jpg

NUJP-oath-taking.jpg

694 ms

IMG_1689.jpg

IMG_1689.jpg

692 ms

Media-monitor.png

Media-monitor.png

739 ms

20150908_093420-1024x614.jpg

20150908_093420-1024x614.jpg

652 ms

20150827_142824.jpg

20150827_142824.jpg

769 ms

zambobadjao3.jpg

zambobadjao3.jpg

668 ms

IMG_0075_resized.jpg

IMG_0075_resized.jpg

422 ms

IMG_7532.jpg

IMG_7532.jpg

503 ms

UmjDGIE_sB8

UmjDGIE_sB8

346 ms

mqdefault.jpg

mqdefault.jpg

416 ms

mqdefault.jpg

mqdefault.jpg

460 ms

mqdefault.jpg

mqdefault.jpg

611 ms

play.png

play.png

637 ms

all.js

all.js

232 ms

www-widgetapi.js

www-widgetapi.js

373 ms

count.js

count.js

327 ms

xd_arbiter.php

xd_arbiter.php

253 ms

xd_arbiter.php

xd_arbiter.php

330 ms

ping

ping

201 ms

foobox.svg

foobox.svg

445 ms

foobox.woff

foobox.woff

458 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

93 ms

www-embed-player.js

www-embed-player.js

119 ms

base.js

base.js

162 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

48 ms

ad_status.js

ad_status.js

47 ms

SEO Factors

cmfr-phil.org 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 Cmfr-phil.org 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 Cmfr-phil.org 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

cmfr-phil.org

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