Tools & Wizards About Us
rise.ph screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

rise.ph

High Speed Fiber Internet Service Provider Philippines - RISE

Page Load Speed

781 ms in total

First Response

25 ms

Resources Loaded

678 ms

Page Rendered

78 ms

rise.ph screenshot

About Website

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

RISE provides you with fast and reliable high speed fiber internet. Our expert team supports you with fast response time.

Visit rise.ph

Key Findings

We analyzed Rise.ph page load time and found that the first response time was 25 ms and then it took 756 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

rise.ph performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value7,690 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

rise.ph

25 ms

rise.ph

51 ms

gtm.js

125 ms

gtm.js

214 ms

1080.js

112 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 26% of them (9 requests) were addressed to the original Rise.ph, 15% (5 requests) were made to Ajax.googleapis.com and 6% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (270 ms) relates to the external source Js.hs-analytics.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.7 kB (7%)

Content Size

254.8 kB

After Optimization

238.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rise.ph main page is 254.8 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. 65% of websites need less resources to load. Javascripts take 228.3 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 8.9 kB

  • Original 12.8 kB
  • After minification 12.8 kB
  • After compression 4.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. 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 8.9 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.9 kB
  • After minification 2.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. RISE images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 7.8 kB

  • Original 228.3 kB
  • After minification 228.2 kB
  • After compression 220.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 10.8 kB
  • After minification 10.8 kB
  • After compression 10.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. Rise.ph has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (90%)

Requests Now

30

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rise.ph

rise.ph

25 ms

rise.ph

rise.ph

51 ms

gtm.js

gtm.js

125 ms

gtm.js

gtm.js

214 ms

1080.js

1080.js

112 ms

bootstrap.min.css

bootstrap.min.css

147 ms

jquery-ui.css

jquery-ui.css

116 ms

all.min.css

all.min.css

31 ms

all.css

all.css

159 ms

style.min.css

style.min.css

89 ms

headerfooter.min.css

headerfooter.min.css

107 ms

css

css

165 ms

jquery.min.js

jquery.min.js

121 ms

jquery-ui.min.js

jquery-ui.min.js

162 ms

bootstrap.min.js

bootstrap.min.js

201 ms

markerclusterer.js

markerclusterer.js

232 ms

angular.min.js

angular.min.js

162 ms

angular-sanitize.min.js

angular-sanitize.min.js

155 ms

vendor.js

vendor.js

109 ms

loader.js

loader.js

113 ms

app.min.js

app.min.js

104 ms

3354227.js

3354227.js

206 ms

libphonenumber-min.js

libphonenumber-min.js

153 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

204 ms

libphonenumber-min.js

libphonenumber-min.js

53 ms

logo-black.png

logo-black.png

38 ms

6373563.js

6373563.js

91 ms

web-interactives-embed.js

web-interactives-embed.js

96 ms

fb.js

fb.js

50 ms

leadflows.js

leadflows.js

56 ms

conversations-embed.js

conversations-embed.js

81 ms

3354227.js

3354227.js

270 ms

banner.js

banner.js

81 ms

main.js

main.js

11 ms

Accessibility Review

rise.ph accessibility score

90

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

rise.ph best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

rise.ph SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

rise.ph

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