Tools & Wizards About Us
data.gov.ph screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

data.gov.ph

Open Data Philippines

Page Load Speed

50.2 sec in total

First Response

1.6 sec

Resources Loaded

48.2 sec

Page Rendered

444 ms

data.gov.ph screenshot

About Website

Click here to check amazing Data content for Philippines. Otherwise, check out these important facts you probably never knew about data.gov.ph

Visit data.gov.ph

Key Findings

We analyzed Data.gov.ph page load time and found that the first response time was 1.6 sec and then it took 48.7 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 were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

data.gov.ph performance score

0

Network Requests Diagram

data.gov.ph

1575 ms

wp-emoji-release.min.js

1461 ms

styles.css

602 ms

app.css

6957 ms

foundation-icons.css

1273 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 73% of them (66 requests) were addressed to the original Data.gov.ph, 8% (7 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Data.gov.ph.

Page Optimization Overview & Recommendations

Page size can be reduced by 886.0 kB (50%)

Content Size

1.8 MB

After Optimization

888.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 59.3 kB

  • Original 74.4 kB
  • After minification 68.0 kB
  • After compression 15.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 59.3 kB or 80% of the original size.

Image Optimization

-27%

Potential reduce by 222.5 kB

  • Original 824.4 kB
  • After minification 601.9 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, Data needs image optimization as it can save up to 222.5 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 518.6 kB

  • Original 770.4 kB
  • After minification 742.9 kB
  • After compression 251.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 518.6 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 85.6 kB

  • Original 105.3 kB
  • After minification 85.2 kB
  • After compression 19.8 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. Data.gov.ph needs all CSS files to be minified and compressed as it can save up to 85.6 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

79

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data. 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 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

data.gov.ph

data.gov.ph

1575 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1461 ms

styles.css

styles.css

602 ms

app.css

app.css

6957 ms

foundation-icons.css

foundation-icons.css

1273 ms

slick.css

slick.css

954 ms

style.css

style.css

2149 ms

font-awesome.min.css

font-awesome.min.css

115 ms

custom.css

custom.css

1262 ms

responsive.css

responsive.css

1546 ms

addtoany.min.css

addtoany.min.css

1948 ms

custom.css

custom.css

1876 ms

jquery.js

jquery.js

5991 ms

jquery-migrate.min.js

jquery-migrate.min.js

3153 ms

modernizr.js

modernizr.js

2437 ms

waypoints.min.js

waypoints.min.js

2566 ms

jquery.orbit-1.3.0.min.js

jquery.orbit-1.3.0.min.js

3028 ms

jquery.form.min.js

jquery.form.min.js

3353 ms

scripts.js

scripts.js

3232 ms

foundation.min.js

foundation.min.js

7254 ms

foundation.equalizer.js

foundation.equalizer.js

3238 ms

foundation.interchange.js

foundation.interchange.js

3759 ms

navigation.js

navigation.js

3556 ms

app.js

app.js

3557 ms

functions.js

functions.js

3864 ms

slick.js

slick.js

5680 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

4025 ms

comment-reply.min.js

comment-reply.min.js

4162 ms

wp-embed.min.js

wp-embed.min.js

4665 ms

count.js

count.js

4475 ms

jquery-ui.js

jquery-ui.js

272 ms

js

js

719 ms

css

css

115 ms

css

css

181 ms

css

css

215 ms

icon-20.png

icon-20.png

899 ms

image-slider-2_0.jpg

image-slider-2_0.jpg

2654 ms

image-slider-3.jpg

image-slider-3.jpg

6511 ms

image-slider-4_0-846x423.jpg

image-slider-4_0-846x423.jpg

3487 ms

Front-Feature-Hackathon.jpg

Front-Feature-Hackathon.jpg

11983 ms

DGPH_Infog_FAiTH_1.jpg

DGPH_Infog_FAiTH_1.jpg

2458 ms

image-slider-1_0-846x423.jpg

image-slider-1_0-846x423.jpg

4733 ms

facebook.png

facebook.png

3578 ms

twitter.png

twitter.png

3603 ms

print.png

print.png

3762 ms

featured-11.png

featured-11.png

5128 ms

data-2.png

data-2.png

9828 ms

data-3.png

data-3.png

17365 ms

footlogo.png

footlogo.png

5390 ms

analytics.js

analytics.js

455 ms

seal-govph.png

seal-govph.png

6620 ms

searchicon.png

searchicon.png

5961 ms

header-bg1.png

header-bg1.png

6558 ms

logo-datagov.png

logo-datagov.png

8477 ms

search-data-bg.png

search-data-bg.png

8298 ms

search-data-text-box.png

search-data-text-box.png

7104 ms

according-down-up.png

according-down-up.png

7362 ms

according-down-arrow.png

according-down-arrow.png

7654 ms

featured-infographics-title-bg.png

featured-infographics-title-bg.png

9603 ms

facebook.png

facebook.png

8606 ms

twitter.png

twitter.png

8767 ms

print.png

print.png

9190 ms

page.js

page.js

227 ms

icon-activities.png

icon-activities.png

9268 ms

icon-plus.png

icon-plus.png

9744 ms

icon-latest-news.png

icon-latest-news.png

10020 ms

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

307 ms

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

157 ms

Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff

Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff

203 ms

vzIUHo9z-oJ4WgkpPOtg13YhjbSpvc47ee6xR_80Hnw.woff

vzIUHo9z-oJ4WgkpPOtg13YhjbSpvc47ee6xR_80Hnw.woff

303 ms

d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff

d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff

302 ms

mnpfi9pxYH-Go5UiibESIrO3LdcAZYWl9Si6vvxL-qU.woff

mnpfi9pxYH-Go5UiibESIrO3LdcAZYWl9Si6vvxL-qU.woff

303 ms

HelveticaNeue.woff

HelveticaNeue.woff

19692 ms

Zd2E9abXLFGSr9G3YK2MsNxB8OB85xaNTJvVSB9YUjQ.woff

Zd2E9abXLFGSr9G3YK2MsNxB8OB85xaNTJvVSB9YUjQ.woff

273 ms

sm13.html

sm13.html

466 ms

collect

collect

356 ms

count.js

count.js

328 ms

ajax-loader.gif

ajax-loader.gif

9902 ms

collect

collect

215 ms

rotator-black.png

rotator-black.png

9818 ms

pause-black.png

pause-black.png

9587 ms

right-arrow.png

right-arrow.png

9888 ms

left-arrow.png

left-arrow.png

9921 ms

infographics-seperator.png

infographics-seperator.png

11130 ms

ga.js

ga.js

213 ms

timer-black.png

timer-black.png

8126 ms

common.js

common.js

262 ms

util.js

util.js

308 ms

stats.js

stats.js

189 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

338 ms

HelveticaNeue.ttf

HelveticaNeue.ttf

19967 ms

SEO Factors

data.gov.ph SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

data.gov.ph

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