Tools & Wizards About Us
lifeguard.sg screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

lifeguard.sg

Lifeguard Singapore | Best Lifesaving Training Courses & Lessons

Page Load Speed

14.2 sec in total

First Response

1.9 sec

Resources Loaded

12 sec

Page Rendered

317 ms

lifeguard.sg screenshot

About Website

Welcome to lifeguard.sg homepage info - get ready to check Lifeguard best content right away, or after learning these important things about lifeguard.sg

Lifeguard Singapore provides a one-stop web-portal to find relevant resources to get your lifesaving certification and useful career advices.

Visit lifeguard.sg

Key Findings

We analyzed Lifeguard.sg page load time and found that the first response time was 1.9 sec and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

lifeguard.sg performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value17.5 s

0/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.137

80/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

www.lifeguard.sg

1884 ms

wp-emoji-release.min.js

233 ms

q-a-plus.css

504 ms

style.min.css

1158 ms

styles.css

717 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 89% of them (49 requests) were addressed to the original Lifeguard.sg, 4% (2 requests) were made to Ssl.google-analytics.com and 2% (1 request) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Lifeguard.sg.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.4 kB (28%)

Content Size

776.2 kB

After Optimization

555.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lifeguard.sg main page is 776.2 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. 25% of websites need less resources to load. Javascripts take 293.8 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 132.9 kB

  • Original 152.4 kB
  • After minification 149.7 kB
  • After compression 19.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. 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 132.9 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 10.9 kB

  • Original 281.0 kB
  • After minification 270.1 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. Lifeguard images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 46.0 kB

  • Original 293.8 kB
  • After minification 293.7 kB
  • After compression 247.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 46.0 kB or 16% of the original size.

CSS Optimization

-62%

Potential reduce by 30.6 kB

  • Original 49.1 kB
  • After minification 49.0 kB
  • After compression 18.5 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. Lifeguard.sg needs all CSS files to be minified and compressed as it can save up to 30.6 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (79%)

Requests Now

53

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.lifeguard.sg

www.lifeguard.sg

1884 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

233 ms

q-a-plus.css

q-a-plus.css

504 ms

style.min.css

style.min.css

1158 ms

styles.css

styles.css

717 ms

settings.css

settings.css

715 ms

captions.css

captions.css

725 ms

style.css

style.css

766 ms

style.css

style.css

772 ms

blue.css

blue.css

949 ms

mobile.css

mobile.css

949 ms

tablet.css

tablet.css

969 ms

default.min.css

default.min.css

1023 ms

column-style.css

column-style.css

1024 ms

jquery.js

jquery.js

1546 ms

jquery-migrate.min.js

jquery-migrate.min.js

1231 ms

TweenMax.min.js

TweenMax.min.js

1444 ms

pieces.wp.animations.js

pieces.wp.animations.js

1563 ms

pieces.wp.min.js

pieces.wp.min.js

1280 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

2528 ms

rollinglinks.js

rollinglinks.js

1473 ms

jquery.coda-slider-3.0.js

jquery.coda-slider-3.0.js

1530 ms

jquery.tools.min.js

jquery.tools.min.js

1688 ms

jquery-ui-1.10.2.js

jquery-ui-1.10.2.js

2407 ms

slider.js

slider.js

1761 ms

jflow.plus.js

jflow.plus.js

1799 ms

opacity.js

opacity.js

1797 ms

tooltip.js

tooltip.js

1955 ms

backtotop.js

backtotop.js

1993 ms

external-tracking.min.js

external-tracking.min.js

2047 ms

buttons.js

buttons.js

21 ms

loader.js

loader.js

21 ms

q-a-plus.js

q-a-plus.js

2031 ms

comment-reply.min.js

comment-reply.min.js

2203 ms

scripts.js

scripts.js

2225 ms

wp-embed.min.js

wp-embed.min.js

2270 ms

ga.js

ga.js

47 ms

lifeguardlogo-300x139.png

lifeguardlogo-300x139.png

466 ms

beyond_fb.png

beyond_fb.png

255 ms

lifeguard_singapore_home.jpg

lifeguard_singapore_home.jpg

950 ms

red-arrow-final.gif

red-arrow-final.gif

256 ms

Junior-Lifeguard-580x400-80x80.jpg

Junior-Lifeguard-580x400-80x80.jpg

272 ms

68th-LS123-Intensive-Student-80x80.jpg

68th-LS123-Intensive-Student-80x80.jpg

494 ms

b6.jpg

b6.jpg

1421 ms

init.js

init.js

47 ms

1.gif

1.gif

475 ms

4.gif

4.gif

475 ms

6.gif

6.gif

478 ms

2.gif

2.gif

681 ms

5.gif

5.gif

700 ms

8.gif

8.gif

723 ms

260e.svg

260e.svg

28 ms

beyond_up.png

beyond_up.png

691 ms

__utm.gif

__utm.gif

14 ms

beyond_bullet.png

beyond_bullet.png

257 ms

Accessibility Review

lifeguard.sg accessibility score

48

Accessibility Issues

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.

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

lifeguard.sg 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lifeguard.sg SEO score

93

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

Image elements do not have [alt] attributes

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

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 Lifeguard.sg 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 Lifeguard.sg 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

lifeguard.sg

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