6.3 sec in total
393 ms
5.7 sec
173 ms
Welcome to fmglobal.sg homepage info - get ready to check FM Global best content right away, or after learning these important things about fmglobal.sg
You’re focused on growing your business. FM is focused on bringing you commercial property insurance solutions tailored for your business, with industry-specific expertise to help you build resilience...
Visit fmglobal.sgWe analyzed Fmglobal.sg page load time and found that the first response time was 393 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fmglobal.sg performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value13.8 s
0/100
25%
Value22.3 s
0/100
10%
Value1,330 ms
17/100
30%
Value0.022
100/100
15%
Value35.9 s
0/100
10%
393 ms
34 ms
233 ms
482 ms
157 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 94% of them (147 requests) were addressed to the original Fmglobal.sg, 2% (3 requests) were made to Cdn.cookielaw.org and 1% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Fmglobal.sg.
Page size can be reduced by 2.3 MB (52%)
4.3 MB
2.1 MB
In fact, the total size of Fmglobal.sg main page is 4.3 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. 55% of websites need less resources to load. Javascripts take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 72.7 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 30.6 kB, which is 36% 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 72.7 kB or 86% of the original size.
Potential reduce by 3.2 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. FM Global images are well optimized though.
Potential reduce by 1.9 MB
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 1.9 MB or 61% of the original size.
Potential reduce by 330.7 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. Fmglobal.sg needs all CSS files to be minified and compressed as it can save up to 330.7 kB or 81% of the original size.
Number of requests can be reduced by 133 (93%)
143
10
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FM Global. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 118 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.fmglobal.sg
393 ms
font-awesome.min.css
34 ms
mediaelementplayer.css
233 ms
mediaelementplayer-legacy.css
482 ms
font-awesomemin.css
157 ms
fullcalendar.css
403 ms
jquerymCustomScrollbar.css
149 ms
jquery-ui.css
281 ms
author.css
315 ms
core.css
448 ms
file-type-icons.css
412 ms
grayscale-mode.css
521 ms
reset.css
450 ms
fmg-style.css
766 ms
nathazglobal.css
779 ms
subscription.css
614 ms
ruxitagentjs_ICA2NVfqru_10283240117152214.js
1034 ms
VisitorIdentification.js
628 ms
OtAutoBlock.js
130 ms
otSDKStub.js
141 ms
index.min.js
34 ms
ie-origin-fix.js
694 ms
xaquery.js
1313 ms
moment.js
919 ms
lo-dash.js
962 ms
modernizr.js
1145 ms
galleria-161.js
1144 ms
fullcalendar.js
1395 ms
gcal.js
1146 ms
jqueryuitouch-punchmin.js
1172 ms
hammer.js
1420 ms
backbone-min.js
1395 ms
typeahead.js
1295 ms
jquerymCustomScrollbar.js
1464 ms
flash-polyfill.js
1428 ms
mediaelement-and-player.js
1645 ms
dailymotion.js
1659 ms
facebook.js
1658 ms
soundcloud.js
1633 ms
twitch.js
1593 ms
vimeo.js
1659 ms
xa.js
1681 ms
observer.js
1692 ms
partial-design-highlight.js
1550 ms
google-maps-connector.js
1636 ms
component-location-service.js
1729 ms
component-map.js
1424 ms
component-location-service.js
1727 ms
component-search.js
1642 ms
component-search-ajax.js
1553 ms
component-search-base-model.js
1490 ms
component-search-base-view.js
1737 ms
component-search-box.js
1509 ms
component-search-facet-data.js
1556 ms
component-search-facet-summary.js
1647 ms
css2
25 ms
css2
36 ms
component-search-facet-dropdown.js
1438 ms
component-search-facet-managed-range.js
1557 ms
component-search-facet-range-slider.js
1339 ms
component-search-facet-slider.js
1396 ms
d7f5b0e5-d34f-4bc1-ae0a-f82c039ccdae.json
86 ms
component-search-load-more.js
1293 ms
component-search-location-filter.js
1295 ms
component-search-page-selector.js
1261 ms
component-search-page-size.js
1335 ms
fontawesome-webfont.woff
13 ms
9YNLL0bmRhcAAfTIrgAAAA=
1 ms
component-search-parameters.js
1682 ms
component-search-query.js
1218 ms
component-search-radius-filter.js
1159 ms
component-search-results-count.js
1195 ms
component-search-results-filter.js
1186 ms
component-search-sort.js
1241 ms
component-search-url.js
1262 ms
component-search-results.js
1252 ms
component-search-variant-filter.js
1135 ms
component-search-service.js
1133 ms
component-search-router.js
1185 ms
component-search-facet-daterange.js
1183 ms
accessibility.js
1237 ms
component-accordions.js
1206 ms
component-archive.js
1120 ms
component-breadcrumb.js
1358 ms
component-carousel.js
1176 ms
component-container.js
1128 ms
component-disqus.js
1201 ms
component-facebook.js
1041 ms
component-flash.js
1160 ms
component-flip.js
1055 ms
component-fullcalendar.js
1211 ms
component-galleria.js
1090 ms
component-language-selector.js
1081 ms
component-navigation.js
1061 ms
component-overlay.js
1103 ms
component-snippet.js
1182 ms
component-social.js
1072 ms
component-tabs.js
1064 ms
component-toggle.js
1123 ms
component-video.js
1049 ms
component-video-playlist.js
1061 ms
details-polyfill.js
1032 ms
fixheight.js
1324 ms
search-fixheight.js
1057 ms
resolveconflicts.js
1132 ms
brightcove-script.js
1347 ms
fix-js-links.js
1019 ms
jquery-341min.js
1023 ms
brightcove.js
1787 ms
component-tabs.js
1181 ms
jquery-validate-min.js
1061 ms
jquery-validate.js
1049 ms
JqueryUnobstrusive.js
1119 ms
jquery-unobstusive-ajax-min.js
1110 ms
form-validate.js
1045 ms
form-tracking.js
1199 ms
form-conditions.js
1386 ms
modernizrcustom77728.js
1101 ms
owlcarousel1.js
1354 ms
PrintShare.js
1087 ms
scrollSmoothTo.js
1109 ms
sitewide-results-count.js
1212 ms
skrollrmin.js
1155 ms
subscription-form.js
1141 ms
mediamatchmin.js
1194 ms
enquiremin.js
1328 ms
FMGScriptMin.js
1354 ms
sort-select-elements.js
1185 ms
d365form-why-fm-global.js
1130 ms
natHazScript.js
1209 ms
climate-form.js
1208 ms
handle-cookie-links.js
1240 ms
jquery.validate.min.js
1591 ms
jquery.validate.unobtrusive.min.js
1531 ms
jquery.unobtrusive-ajax.min.js
1188 ms
form.validate.js
1174 ms
form.tracking.js
1198 ms
form.conditions.js
1333 ms
RobotoCondensed-Regular-webfont.woff
1151 ms
fontawesome-webfont-woff.woff
1167 ms
fm-global.woff
1173 ms
fm-global.svg
1250 ms
Roboto-Bold-webfont.woff
1055 ms
RobotoCondensed-Bold-webfont.woff
1057 ms
fm-logo-purple-site-logo.svg
1146 ms
Resilience-Credit-2000x889.jpg
1035 ms
Resilience-Index_HP-banner.jpg
1044 ms
world-peace-2000-x-889.jpg
1170 ms
Reason_icon.png
1034 ms
Newsletter_icon.png
1010 ms
data-sheets_icon.png
1018 ms
product_update.png
958 ms
RobotoCondensed-Regular-webfont.ttf
335 ms
Roboto-Bold-webfont.ttf
190 ms
Roboto-Bold-webfont.svg
258 ms
RobotoCondensed-Regular-webfont.svg
224 ms
fmglobal.sg accessibility score
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
[aria-*] attributes are not valid or misspelled
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fmglobal.sg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fmglobal.sg SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fmglobal.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 Fmglobal.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.
fmglobal.sg
Open Graph description is not detected on the main page of FM Global. 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: