Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

stomp.sg

Stomp - Activating Singapore's Most Awesome Citizen Journalists

Page Load Speed

12.1 sec in total

First Response

501 ms

Resources Loaded

8.5 sec

Page Rendered

3.1 sec

stomp.sg screenshot

About Website

Visit stomp.sg now to see the best up-to-date Stomp content and also check out these interesting facts you probably never knew about stomp.sg

Stomp - Read the latest local news & interesting stories in Singapore includes Get Inspired and more only at STOMP.

Visit stomp.sg

Key Findings

We analyzed Stomp.sg page load time and found that the first response time was 501 ms and then it took 11.6 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

stomp.sg performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.7 s

0/100

25%

SI (Speed Index)

Value20.6 s

0/100

10%

TBT (Total Blocking Time)

Value11,480 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.328

35/100

15%

TTI (Time to Interactive)

Value44.0 s

0/100

10%

Network Requests Diagram

stomp.sg

501 ms

stomp.straitstimes.com

232 ms

ads_checker.js

866 ms

system.base.css

105 ms

ls.aspectratio.css

265 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Stomp.sg, 45% (73 requests) were made to Stomp.straitstimes.com and 29% (46 requests) were made to Img.stomp.com.sg. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Img.stomp.com.sg.

Page Optimization Overview & Recommendations

Page size can be reduced by 731.4 kB (18%)

Content Size

4.1 MB

After Optimization

3.4 MB

In fact, the total size of Stomp.sg main page is 4.1 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. Only a small number of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 239.4 kB

  • Original 360.2 kB
  • After minification 359.7 kB
  • After compression 120.8 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 239.4 kB or 66% of the original size.

Image Optimization

-7%

Potential reduce by 216.3 kB

  • Original 3.3 MB
  • After minification 3.1 MB

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. Stomp images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 172.1 kB

  • Original 350.6 kB
  • After minification 332.2 kB
  • After compression 178.5 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 172.1 kB or 49% of the original size.

CSS Optimization

-73%

Potential reduce by 103.6 kB

  • Original 142.5 kB
  • After minification 142.2 kB
  • After compression 38.9 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. Stomp.sg needs all CSS files to be minified and compressed as it can save up to 103.6 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 80 (54%)

Requests Now

148

After Optimization

68

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

Accessibility Review

stomp.sg accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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

<frame> or <iframe> elements do not have a title

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

stomp.sg best practices score

50

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

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

stomp.sg SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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

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