Tools & Wizards About Us
fnetrade.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

fnetrade.com

TREC holder of Pakistan Stock Exchange|Online Trading Platform

Page Load Speed

2.7 sec in total

First Response

207 ms

Resources Loaded

2.1 sec

Page Rendered

463 ms

fnetrade.com screenshot

About Website

Visit fnetrade.com now to see the best up-to-date Fnetrade content for Pakistan and also check out these interesting facts you probably never knew about fnetrade.com

First National Equities Limited (FNEL) is a leading online stock trading and brokerage firm in Pakistan We bring you the most authentic data and latest updates of PSX.

Visit fnetrade.com

Key Findings

We analyzed Fnetrade.com page load time and found that the first response time was 207 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

fnetrade.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value9.4 s

30/100

10%

Network Requests Diagram

fnetrade.com

207 ms

fnetrade.com

423 ms

js

57 ms

morris.css

71 ms

plugins.css

427 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 68% of them (38 requests) were addressed to the original Fnetrade.com, 25% (14 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fnetrade.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.9 kB (16%)

Content Size

729.5 kB

After Optimization

615.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fnetrade.com main page is 729.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 371.9 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 51.9 kB

  • Original 59.5 kB
  • After minification 29.7 kB
  • After compression 7.6 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 29.8 kB, which is 50% 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 51.9 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 24.9 kB

  • Original 371.9 kB
  • After minification 347.0 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. Fnetrade images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 22.8 kB

  • Original 188.2 kB
  • After minification 188.2 kB
  • After compression 165.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 22.8 kB or 12% of the original size.

CSS Optimization

-13%

Potential reduce by 14.4 kB

  • Original 109.9 kB
  • After minification 109.9 kB
  • After compression 95.5 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. Fnetrade.com needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (49%)

Requests Now

35

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fnetrade.com

fnetrade.com

207 ms

fnetrade.com

fnetrade.com

423 ms

js

js

57 ms

morris.css

morris.css

71 ms

plugins.css

plugins.css

427 ms

style.css

style.css

661 ms

jquery.jConveyorTicker.css

jquery.jConveyorTicker.css

289 ms

FNELOGOTrans.png

FNELOGOTrans.png

501 ms

jquery.js

jquery.js

488 ms

plugins.js

plugins.js

602 ms

raphael.min.js

raphael.min.js

554 ms

morris.min.js

morris.min.js

532 ms

highcharts.js

highcharts.js

65 ms

Charts.js

Charts.js

602 ms

functions.js

functions.js

1085 ms

vegas.min.css

vegas.min.css

655 ms

vegas.min.js

vegas.min.js

675 ms

jquery.jConveyorTicker.js

jquery.jConveyorTicker.js

692 ms

toastr.css

toastr.css

819 ms

toastr.js

toastr.js

819 ms

Common.js

Common.js

818 ms

open.jpeg

open.jpeg

1065 ms

BOD.jpg

BOD.jpg

819 ms

news.jpg

news.jpg

1040 ms

onlinestocktrading.jpg

onlinestocktrading.jpg

1075 ms

PakistanStockMarket-PSX.jpg

PakistanStockMarket-PSX.jpg

1063 ms

trading%20of%20equities.jpg

trading%20of%20equities.jpg

1048 ms

service-desk-06.jpg

service-desk-06.jpg

1159 ms

css

css

35 ms

world-map-dark.png

world-map-dark.png

132 ms

dropdown-arrow.png

dropdown-arrow.png

430 ms

pxiByp8kv8JHgFVrLCz7Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLCz7Z1xlE92JQEk.woff

32 ms

pxiByp8kv8JHgFVrLCz7Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLCz7Z1JlE92JQEl8qw.woff

46 ms

pxiByp8kv8JHgFVrLDD4Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLDD4Z1xlE92JQEk.woff

77 ms

pxiByp8kv8JHgFVrLDD4Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLDD4Z1JlE92JQEl8qw.woff

90 ms

pxiByp8kv8JHgFVrLEj6Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLEj6Z1xlE92JQEk.woff

92 ms

pxiByp8kv8JHgFVrLEj6Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLEj6Z1JlE92JQEl8qw.woff

91 ms

pxiByp8kv8JHgFVrLGT9Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLGT9Z1xlE92JQEk.woff

90 ms

pxiByp8kv8JHgFVrLGT9Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLGT9Z1JlE92JQEl8qw.woff

91 ms

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

92 ms

pxiEyp8kv8JHgFVrJJnedHFHGPezSQ.woff

pxiEyp8kv8JHgFVrJJnedHFHGPezSQ.woff

93 ms

pxiByp8kv8JHgFVrLFj_Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLFj_Z1xlE92JQEk.woff

93 ms

pxiByp8kv8JHgFVrLFj_Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLFj_Z1JlE92JQEl8qw.woff

135 ms

pxiGyp8kv8JHgFVrLPTucHtGOvWDSA.woff

pxiGyp8kv8JHgFVrLPTucHtGOvWDSA.woff

93 ms

pxiGyp8kv8JHgFVrLPTufntGOvWDSHFF.woff

pxiGyp8kv8JHgFVrLPTufntGOvWDSHFF.woff

133 ms

inspiro-icons.ttf

inspiro-icons.ttf

401 ms

fa-solid-900.woff

fa-solid-900.woff

413 ms

fa-regular-400.woff

fa-regular-400.woff

347 ms

fa-brands-400.woff

fa-brands-400.woff

441 ms

GetChartDataKSE30

GetChartDataKSE30

139 ms

GetChartDataKMi30

GetChartDataKMi30

136 ms

GetChartAllShares

GetChartAllShares

169 ms

GetChartDataKSE100

GetChartDataKSE100

180 ms

GetLeaderVolumeValue

GetLeaderVolumeValue

296 ms

GetActiveSectorData

GetActiveSectorData

206 ms

slide2.jpg

slide2.jpg

258 ms

Accessibility Review

fnetrade.com accessibility score

59

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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

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.

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

fnetrade.com best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fnetrade.com SEO score

68

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 Fnetrade.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 Fnetrade.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

fnetrade.com

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