Tools & Wizards About Us
sti.edu screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

sti.edu

STI College. Be Future-Ready. Be STI.

Page Load Speed

26.6 sec in total

First Response

2 sec

Resources Loaded

23.9 sec

Page Rendered

697 ms

sti.edu screenshot

About Website

Welcome to sti.edu homepage info - get ready to check STI best content for Philippines right away, or after learning these important things about sti.edu

Be future-ready with one of the largest network of schools in the Philippines.

Visit sti.edu

Key Findings

We analyzed Sti.edu page load time and found that the first response time was 2 sec and then it took 24.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number 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

sti.edu performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value1,370 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.18

67/100

15%

TTI (Time to Interactive)

Value30.3 s

0/100

10%

Network Requests Diagram

sti.edu

2025 ms

bootstrap.min.css

2130 ms

style.css

933 ms

animate.min.css

1198 ms

css

56 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 32% of them (38 requests) were addressed to the original Sti.edu, 25% (29 requests) were made to Maps.google.com and 8% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Sti.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 873.3 kB (43%)

Content Size

2.0 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sti.edu main page is 2.0 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. 60% of websites need less resources to load. Javascripts take 871.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 68.4 kB

  • Original 81.3 kB
  • After minification 62.6 kB
  • After compression 12.9 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 18.7 kB, which is 23% 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 68.4 kB or 84% of the original size.

Image Optimization

-12%

Potential reduce by 104.2 kB

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

JavaScript Optimization

-59%

Potential reduce by 516.8 kB

  • Original 871.4 kB
  • After minification 868.2 kB
  • After compression 354.6 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 516.8 kB or 59% of the original size.

CSS Optimization

-85%

Potential reduce by 183.9 kB

  • Original 216.5 kB
  • After minification 202.8 kB
  • After compression 32.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. Sti.edu needs all CSS files to be minified and compressed as it can save up to 183.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (50%)

Requests Now

98

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sti.edu

sti.edu

2025 ms

bootstrap.min.css

bootstrap.min.css

2130 ms

style.css

style.css

933 ms

animate.min.css

animate.min.css

1198 ms

css

css

56 ms

font-awesome.min.css

font-awesome.min.css

748 ms

brand

brand

18 ms

brand

brand

24 ms

jquery-1.10.2.js

jquery-1.10.2.js

1128 ms

jquery.appear.js

jquery.appear.js

579 ms

foundation.min.js

foundation.min.js

1659 ms

bootstrap.min.js

bootstrap.min.js

1066 ms

js

js

85 ms

main.js

main.js

1063 ms

googlemaps.js

googlemaps.js

1551 ms

conversion.js

conversion.js

70 ms

fbds.js

fbds.js

177 ms

analytics.js

analytics.js

36 ms

stilogo2.png

stilogo2.png

521 ms

slide-2-shs-IT.jpg

slide-2-shs-IT.jpg

3191 ms

slide-2-shs-CULINARY.jpg

slide-2-shs-CULINARY.jpg

3528 ms

slide-2-shs-STEM.jpg

slide-2-shs-STEM.jpg

5123 ms

slide-2-shs-TOURISM.jpg

slide-2-shs-TOURISM.jpg

4397 ms

slide-2-shs-BUSINESS.jpg

slide-2-shs-BUSINESS.jpg

4996 ms

slide21.jpg

slide21.jpg

5198 ms

alumnifeature_.jpg

alumnifeature_.jpg

4205 ms

alumnifeature_.jpg

alumnifeature_.jpg

4955 ms

alumnifeature_.jpg

alumnifeature_.jpg

5659 ms

alumnifeature_.jpg

alumnifeature_.jpg

5522 ms

front_306x191.jpg

front_306x191.jpg

7880 ms

front_306x191.jpg

front_306x191.jpg

7157 ms

front_306x191.jpg

front_306x191.jpg

6196 ms

e2e.png

e2e.png

6566 ms

logos-ched.png

logos-ched.png

7974 ms

tuv_logo.png

tuv_logo.png

7686 ms

mobile-icons-googleplay.png

mobile-icons-googleplay.png

6614 ms

mobile-icons-appstore.png

mobile-icons-appstore.png

6994 ms

scopelite_mobile.png

scopelite_mobile.png

13083 ms

gtm.js

gtm.js

152 ms

ZndThjI_NIg

ZndThjI_NIg

247 ms

e1ShNErzzMM

e1ShNErzzMM

363 ms

tvc2015-bg.jpg

tvc2015-bg.jpg

20069 ms

admissions_global.jpg

admissions_global.jpg

16050 ms

p6.png

p6.png

7895 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

8086 ms

common.js

common.js

43 ms

map.js

map.js

37 ms

util.js

util.js

91 ms

marker.js

marker.js

39 ms

5530bc387f4fdb976900008e.js

5530bc387f4fdb976900008e.js

239 ms

154 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

75 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

112 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

113 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

8008 ms

collect

collect

96 ms

335 ms

onion.js

onion.js

59 ms

openhand_8_8.cur

openhand_8_8.cur

158 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

181 ms

stats.js

stats.js

64 ms

controls.js

controls.js

58 ms

collect

collect

330 ms

www-embed-player-vfl5foy2V.css

www-embed-player-vfl5foy2V.css

222 ms

www-embed-player.js

www-embed-player.js

355 ms

infowindow.js

infowindow.js

31 ms

296 ms

css

css

80 ms

transparent.png

transparent.png

33 ms

red-dot.png

red-dot.png

120 ms

green-dot.png

green-dot.png

102 ms

blue-dot.png

blue-dot.png

104 ms

orange-dot.png

orange-dot.png

102 ms

purple-dot.png

purple-dot.png

162 ms

pink-dot.png

pink-dot.png

161 ms

yellow-dot.png

yellow-dot.png

196 ms

google4.png

google4.png

101 ms

mapcnt6.png

mapcnt6.png

189 ms

sv5.png

sv5.png

189 ms

tmapctrl.png

tmapctrl.png

183 ms

tmapctrl4.png

tmapctrl4.png

185 ms

vt

vt

116 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

74 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

85 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

129 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

220 ms

vt

vt

215 ms

vt

vt

104 ms

vt

vt

220 ms

vt

vt

129 ms

vt

vt

215 ms

vt

vt

216 ms

vt

vt

216 ms

vt

vt

218 ms

vt

vt

239 ms

vt

vt

220 ms

vt

vt

220 ms

vt

vt

220 ms

tagjs

tagjs

143 ms

veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js

veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js

63 ms

ad_status.js

ad_status.js

168 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

120 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

128 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

258 ms

148 ms

adsct

adsct

154 ms

Pug

Pug

107 ms

pixel

pixel

102 ms

cb

cb

47 ms

cb

cb

17 ms

sd

sd

18 ms

ncm

ncm

11 ms

tap.php

tap.php

134 ms

cb

cb

8 ms

QuotaService.RecordEvent

QuotaService.RecordEvent

14 ms

glyphicons-halflings-regular.ttf

glyphicons-halflings-regular.ttf

1677 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

2536 ms

27 ms

Accessibility Review

sti.edu accessibility score

66

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sti.edu best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

sti.edu SEO score

74

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Sti.edu 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 Sti.edu 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

sti.edu

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