Tools & Wizards About Us

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

webfg.com

Welcome to the largest digital ecosystem in the WealthTech sector.

Page Load Speed

2.2 sec in total

First Response

230 ms

Resources Loaded

1.6 sec

Page Rendered

374 ms

About Website

Click here to check amazing Webfg content for India. Otherwise, check out these important facts you probably never knew about webfg.com

With more than 20 years of experience, Allfunds is a unique platform within the WealthTech sector. With the objective of offering access to the world's largest fund distribution network.

Visit webfg.com

Key Findings

We analyzed Webfg.com page load time and found that the first response time was 230 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

webfg.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value11.1 s

5/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

webfg.com

230 ms

311 ms

9JJ4H-D62E5-WMB2N-JVMS8-Y9FL8

47 ms

GB.svg

44 ms

large_new_Hero_c4f4e325f0.png

596 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Webfg.com, 45% (9 requests) were made to Allfunds.com and 35% (7 requests) were made to App.allfunds.com. The less responsive or slowest element that took the longest time to load (596 ms) relates to the external source App.allfunds.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 678.5 kB (35%)

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-74%

Potential reduce by 118.7 kB

  • Original 160.9 kB
  • After minification 160.8 kB
  • After compression 42.2 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 118.7 kB or 74% of the original size.

Image Optimization

-25%

Potential reduce by 269.0 kB

  • Original 1.1 MB
  • After minification 812.8 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. Obviously, Webfg needs image optimization as it can save up to 269.0 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-43%

Potential reduce by 290.9 kB

  • Original 670.3 kB
  • After minification 670.2 kB
  • After compression 379.4 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 290.9 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (44%)

Requests Now

18

After Optimization

10

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

Accessibility Review

webfg.com accessibility score

97

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.

Best Practices

webfg.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

webfg.com SEO score

92

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

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

High

Document uses legible font sizes

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 Webfg.com 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 Webfg.com 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 Webfg. 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: