Tools & Wizards About Us
saintpierre.com.sg screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% 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

  • 88

    SEO

    Google-friendlier than
    65% of websites

saintpierre.com.sg

Michelin Restaurants Singapore | One Fullerton Restaurants | Saint Pierre

Page Load Speed

24.3 sec in total

First Response

3.8 sec

Resources Loaded

20.4 sec

Page Rendered

74 ms

saintpierre.com.sg screenshot

About Website

Click here to check amazing Saint Pierre content for Singapore. Otherwise, check out these important facts you probably never knew about saintpierre.com.sg

Saint Pierre is one of the One Fullerton restaurants in Singapore that was awarded as a Michelin restaurant. Emmanuel Stroobant is the Michelin starred chef who owns this modern french restaurant in S...

Visit saintpierre.com.sg

Key Findings

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

Performance Metrics

saintpierre.com.sg performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value16.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value65.0 s

0/100

25%

SI (Speed Index)

Value43.0 s

0/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

www.saintpierre.com.sg

3845 ms

sbi-styles.min.css

473 ms

style.min.css

1353 ms

styles.css

681 ms

simple-image-popup.css

695 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 90% of them (52 requests) were addressed to the original Saintpierre.com.sg, 3% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (9.2 sec) belongs to the original domain Saintpierre.com.sg.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (22%)

Content Size

5.5 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saintpierre.com.sg main page is 5.5 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. 65% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 67.0 kB

  • Original 85.4 kB
  • After minification 79.6 kB
  • After compression 18.4 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 67.0 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 68.8 kB

  • Original 3.8 MB
  • After minification 3.7 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. Saint Pierre images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 484.8 kB

  • Original 918.9 kB
  • After minification 914.7 kB
  • After compression 434.1 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 484.8 kB or 53% of the original size.

CSS Optimization

-82%

Potential reduce by 600.5 kB

  • Original 729.5 kB
  • After minification 704.5 kB
  • After compression 129.1 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. Saintpierre.com.sg needs all CSS files to be minified and compressed as it can save up to 600.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (59%)

Requests Now

51

After Optimization

21

  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saint Pierre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 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.saintpierre.com.sg

www.saintpierre.com.sg

3845 ms

sbi-styles.min.css

sbi-styles.min.css

473 ms

style.min.css

style.min.css

1353 ms

styles.css

styles.css

681 ms

simple-image-popup.css

simple-image-popup.css

695 ms

wpcf7-redirect-frontend.min.css

wpcf7-redirect-frontend.min.css

708 ms

pum-site.min.css

pum-site.min.css

710 ms

css

css

30 ms

button-styles.css

button-styles.css

717 ms

jquery.min.js

jquery.min.js

1359 ms

jquery-migrate.min.js

jquery-migrate.min.js

1155 ms

plugins.css

plugins.css

1425 ms

style.css

style.css

1184 ms

js

js

81 ms

plugin.min.js

plugin.min.js

1689 ms

main-script.js

main-script.js

1161 ms

index.js

index.js

1352 ms

index.js

index.js

1359 ms

wpcf7r-fe.js

wpcf7r-fe.js

1394 ms

new-tab.js

new-tab.js

1422 ms

core.min.js

core.min.js

1581 ms

site.min.js

site.min.js

1813 ms

api.js

api.js

40 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1625 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1659 ms

wp-polyfill.min.js

wp-polyfill.min.js

1660 ms

index.js

index.js

1809 ms

forms.js

forms.js

1857 ms

dashicons.min.css

dashicons.min.css

1641 ms

font-awesome.min.css

font-awesome.min.css

1415 ms

gtm.js

gtm.js

94 ms

fbevents.js

fbevents.js

95 ms

fancybox_loading.gif

fancybox_loading.gif

342 ms

sbi-sprite.png

sbi-sprite.png

341 ms

SP-Logo-Trasparent.png

SP-Logo-Trasparent.png

553 ms

V0726-Saint-Pierre1141-scaled.jpg

V0726-Saint-Pierre1141-scaled.jpg

801 ms

V0412-Saint-Pierre0127-scaled.jpg

V0412-Saint-Pierre0127-scaled.jpg

1710 ms

V0301-Saint-Pierre35286-1400x1300px.jpg

V0301-Saint-Pierre35286-1400x1300px.jpg

1239 ms

V0913-Saint-Pierre0858-1400x1300px.jpg

V0913-Saint-Pierre0858-1400x1300px.jpg

1435 ms

V1018-Saint-Pierre0990-1400x1300px-1.jpg

V1018-Saint-Pierre0990-1400x1300px-1.jpg

1038 ms

SaintPierre-DI-0309-ShanDI-3-scaled.jpg

SaintPierre-DI-0309-ShanDI-3-scaled.jpg

1514 ms

FooterLogoUpdated.png

FooterLogoUpdated.png

1059 ms

SP-WhatsApp-Small-Button-1.png

SP-WhatsApp-Small-Button-1.png

1303 ms

SP-Website-Facebook-Icon.png

SP-Website-Facebook-Icon.png

1315 ms

SP-Website-Instagram-Icon.png

SP-Website-Instagram-Icon.png

1469 ms

SP-XHS-Icon.png

SP-XHS-Icon.png

1541 ms

Saint-Piere_Zen-circle_June2023-NEW_optimized_2.gif

Saint-Piere_Zen-circle_June2023-NEW_optimized_2.gif

9165 ms

GothamBook.woff

GothamBook.woff

1608 ms

Gotham-Medium.woff

Gotham-Medium.woff

1643 ms

MrsEavesRoman.woff

MrsEavesRoman.woff

1695 ms

MrsEaves-Bold.woff

MrsEaves-Bold.woff

1721 ms

Gotham-Light.woff

Gotham-Light.woff

1702 ms

recaptcha__en.js

recaptcha__en.js

76 ms

slick-nav.png

slick-nav.png

1646 ms

ajax-loader.gif

ajax-loader.gif

1657 ms

slick.woff

slick.woff

1680 ms

mCSB_home_buttons.png

mCSB_home_buttons.png

8846 ms

ui.totop.png

ui.totop.png

8849 ms

Accessibility Review

saintpierre.com.sg accessibility score

90

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.

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

saintpierre.com.sg 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

SEO Factors

saintpierre.com.sg SEO score

88

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

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 Saintpierre.com.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 Saintpierre.com.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

saintpierre.com.sg

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