5 sec in total
310 ms
3.7 sec
1 sec
Welcome to fwu.life homepage info - get ready to check FWU best content right away, or after learning these important things about fwu.life
Life Insurance products designed for you. FWU brings you the benefits of state-of-the-art investment technology and flexible options according to your personal
Visit fwu.lifeWe analyzed Fwu.life page load time and found that the first response time was 310 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fwu.life performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value4.1 s
47/100
25%
Value10.5 s
7/100
10%
Value9,330 ms
0/100
30%
Value0.091
92/100
15%
Value32.1 s
0/100
10%
310 ms
481 ms
33 ms
77 ms
48 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Fwu.life, 45% (29 requests) were made to D1fwlmkz0ogy1.cloudfront.net and 17% (11 requests) were made to Images.ctfassets.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Googletagmanager.com.
Page size can be reduced by 411.2 kB (29%)
1.4 MB
1.0 MB
In fact, the total size of Fwu.life main page is 1.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 322.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. 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 322.7 kB or 92% of the original size.
Potential reduce by 88.4 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. FWU images are well optimized though.
Potential reduce by 50 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 21 B
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. Fwu.life has all CSS files already compressed.
Number of requests can be reduced by 38 (69%)
55
17
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FWU. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and as a result speed up the page load time.
fwu.life
310 ms
fwu.life
481 ms
33 ms
sanitize.css@7
77 ms
styles.css
48 ms
687.js
66 ms
polyfills.js
48 ms
addScriptOnEventCreate.js
49 ms
loadingSpinner.js
41 ms
addInternetExplorerWelcomeScreen.js
31 ms
index.js
31 ms
index.js
32 ms
index.js
35 ms
index.js
38 ms
index.js
39 ms
index.js
41 ms
index.js
43 ms
index.js
45 ms
index.js
45 ms
index.js
46 ms
index.js
56 ms
index.js
52 ms
index.js
47 ms
index.js
50 ms
index.js
48 ms
index.js
48 ms
index.js
53 ms
index.js
55 ms
index.js
55 ms
addInviewEventListenerToElement.js
56 ms
sanitize.css@7.0.3
20 ms
sanitize.css
14 ms
gtm.js
1983 ms
test-teaser_0.png
1973 ms
dvIHed9NGxA
1583 ms
MicrosoftTeams-image__6_.png
435 ms
quote_annabel.png
543 ms
quote_frank-v01.png
542 ms
04_Alternative_category_colour_0d76fc.png
417 ms
02_Alternative_category_colour_00fc92.png
416 ms
20221213_cfi_SoMe_Post_v13.jpg
437 ms
fwu_logo.svg
696 ms
fwu_instagram.png
427 ms
fwu_linkedin.png
436 ms
fwu_youtube.png
535 ms
BrandonText-Light.woff
219 ms
BrandonText-Medium.woff
219 ms
BrandonText-Bold.woff
219 ms
js
63 ms
js
160 ms
analytics.js
154 ms
uc.js
151 ms
6918113.js
150 ms
hotjar-2689806.js
150 ms
collect
184 ms
modules.2472296d2d26f0040059.js
79 ms
fb.js
89 ms
leadflows.js
100 ms
banner.js
197 ms
6918113.js
125 ms
collectedforms.js
100 ms
collect
51 ms
js
50 ms
ga-audiences
88 ms
fwu.life 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fwu.life best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fwu.life SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fwu.life 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 Fwu.life 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.
fwu.life
Open Graph description is not detected on the main page of FWU. 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: