Tools & Wizards About Us
w3.neda.gov.ph screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

w3.neda.gov.ph

NEDA IAMS

Page Load Speed

32.1 sec in total

First Response

6 sec

Resources Loaded

25.9 sec

Page Rendered

258 ms

w3.neda.gov.ph screenshot

About Website

Welcome to w3.neda.gov.ph homepage info - get ready to check W 3 NEDA best content for Philippines right away, or after learning these important things about w3.neda.gov.ph

Visit w3.neda.gov.ph

Key Findings

We analyzed W3.neda.gov.ph page load time and found that the first response time was 6 sec and then it took 26.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

w3.neda.gov.ph performance score

0

Network Requests Diagram

w3.neda.gov.ph

5950 ms

default.css

569 ms

default_var.js

1126 ms

menu_com.js

1124 ms

widget.js

25 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 56% of them (35 requests) were addressed to the original W3.neda.gov.ph, 33% (21 requests) were made to Neda.gov.ph and 3% (2 requests) were made to Xyz.freeweblogger.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source S13.sitemeter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.4 kB (65%)

Content Size

291.3 kB

After Optimization

102.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of W3.neda.gov.ph main page is 291.3 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. 15% of websites need less resources to load. Images take 115.6 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 63.6 kB

  • Original 74.1 kB
  • After minification 57.7 kB
  • After compression 10.5 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 16.4 kB, which is 22% 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.6 kB or 86% of the original size.

Image Optimization

-59%

Potential reduce by 68.4 kB

  • Original 115.6 kB
  • After minification 47.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, W 3 NEDA needs image optimization as it can save up to 68.4 kB or 59% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 55.3 kB

  • Original 100.2 kB
  • After minification 90.2 kB
  • After compression 44.9 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 55.3 kB or 55% of the original size.

CSS Optimization

-77%

Potential reduce by 1.0 kB

  • Original 1.3 kB
  • After minification 1.1 kB
  • After compression 309 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. W3.neda.gov.ph needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (45%)

Requests Now

40

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

w3.neda.gov.ph

w3.neda.gov.ph

5950 ms

default.css

default.css

569 ms

default_var.js

default_var.js

1126 ms

menu_com.js

menu_com.js

1124 ms

widget.js

widget.js

25 ms

about_link.gif

about_link.gif

233 ms

econreport_link.gif

econreport_link.gif

675 ms

progsprj_link.gif

progsprj_link.gif

676 ms

references_link.gif

references_link.gif

457 ms

sitemap_link.gif

sitemap_link.gif

524 ms

home_default.gif

home_default.gif

677 ms

go2007.gif

go2007.gif

757 ms

intranet.jpg

intranet.jpg

1378 ms

eforum_icon.jpg

eforum_icon.jpg

1356 ms

bid2s.jpg

bid2s.jpg

1137 ms

inpi.jpg

inpi.jpg

1015 ms

E-Mail2_.png

E-Mail2_.png

2409 ms

ootp2010.jpg

ootp2010.jpg

1010 ms

transseal.gif

transseal.gif

1244 ms

nedaservices2007s.jpg

nedaservices2007s.jpg

1255 ms

NEDAknowledgecenter.jpg

NEDAknowledgecenter.jpg

1388 ms

nedaphotorelease.jpg

nedaphotorelease.jpg

1479 ms

transparent_shim.gif

transparent_shim.gif

1475 ms

more.jpg

more.jpg

1589 ms

DGpic.jpg

DGpic.jpg

2811 ms

webcrop.jpg

webcrop.jpg

1546 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

1412 ms

amb3.gif

amb3.gif

4276 ms

ke2009.jpg

ke2009.jpg

4285 ms

mdgs.gif

mdgs.gif

5230 ms

mdg_icon.jpg

mdg_icon.jpg

5202 ms

IO_SIMULATOR.GIF

IO_SIMULATOR.GIF

5367 ms

ncpedslink.jpg

ncpedslink.jpg

5437 ms

pcsd09.jpg

pcsd09.jpg

6562 ms

CAFlogo.jpg

CAFlogo.jpg

6553 ms

2012-cbpi-logo_50x50.jpg

2012-cbpi-logo_50x50.jpg

6624 ms

jica.gif

jica.gif

6697 ms

MSDF.jpg

MSDF.jpg

7701 ms

PLPEM%20cover%20page.jpg

PLPEM%20cover%20page.jpg

7905 ms

drr.jpg

drr.jpg

7869 ms

hgdg_link.jpg

hgdg_link.jpg

7964 ms

idap.gif

idap.gif

8004 ms

devpulse2007.jpg

devpulse2007.jpg

9003 ms

pfmjuan.gif

pfmjuan.gif

8997 ms

index.php

index.php

144 ms

script.php

script.php

139 ms

counter.js

counter.js

3 ms

counter.js

counter.js

19881 ms

pfmp.jpg

pfmp.jpg

9254 ms

gix2007.gif

gix2007.gif

9189 ms

facebook.jpg

facebook.jpg

9212 ms

twitter.jpg

twitter.jpg

10245 ms

black_dot_vertical.gif

black_dot_vertical.gif

1394 ms

nedalogo.jpg

nedalogo.jpg

1053 ms

bg_ru_corner.gif

bg_ru_corner.gif

1076 ms

graydot_vertical.gif

graydot_vertical.gif

1127 ms

dot.gif

dot.gif

1135 ms

dot2.gif

dot2.gif

1251 ms

dot22.gif

dot22.gif

1285 ms

prsep.gif

prsep.gif

1345 ms

graydot_horizontal.gif

graydot_horizontal.gif

1353 ms

t.php

t.php

105 ms

ga.js

ga.js

5 ms

SEO Factors

w3.neda.gov.ph SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise W3.neda.gov.ph 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 W3.neda.gov.ph 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

w3.neda.gov.ph

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