Tools & Wizards About Us
fgb.net screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    55% of websites

fgb.net

First Guaranty Bank

Page Load Speed

2.5 sec in total

First Response

77 ms

Resources Loaded

1.9 sec

Page Rendered

554 ms

fgb.net screenshot

About Website

Click here to check amazing Fgb content for United States. Otherwise, check out these important facts you probably never knew about fgb.net

With over 89 years of experience, First Guaranty Bank has the skills and expertise to help you reach your financial goals.

Visit fgb.net

Key Findings

We analyzed Fgb.net page load time and found that the first response time was 77 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

fgb.net performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value25.2 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

fgb.net

77 ms

www.fgb.net

301 ms

css

46 ms

main.min.css

89 ms

osano.js

130 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 46% of them (31 requests) were addressed to the original Fgb.net, 24% (16 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to App.five9.com. The less responsive or slowest element that took the longest time to load (424 ms) relates to the external source Wt.dm00.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (12%)

Content Size

9.3 MB

After Optimization

8.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fgb.net main page is 9.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. 75% 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 8.8 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 228.2 kB

  • Original 316.1 kB
  • After minification 300.2 kB
  • After compression 88.0 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 228.2 kB or 72% of the original size.

Image Optimization

-9%

Potential reduce by 774.5 kB

  • Original 8.8 MB
  • After minification 8.0 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. Fgb images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 92.6 kB

  • Original 157.2 kB
  • After minification 157.1 kB
  • After compression 64.6 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 92.6 kB or 59% of the original size.

CSS Optimization

-35%

Potential reduce by 11.5 kB

  • Original 32.6 kB
  • After minification 32.5 kB
  • After compression 21.0 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. Fgb.net needs all CSS files to be minified and compressed as it can save up to 11.5 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (42%)

Requests Now

48

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fgb.net

fgb.net

77 ms

www.fgb.net

www.fgb.net

301 ms

css

css

46 ms

main.min.css

main.min.css

89 ms

osano.js

osano.js

130 ms

common.js

common.js

129 ms

js

js

61 ms

ScriptResource.axd

ScriptResource.axd

324 ms

ScriptResource.axd

ScriptResource.axd

323 ms

tracking.js

tracking.js

424 ms

First_Guaranty_Bank.js

First_Guaranty_Bank.js

33 ms

gtm.js

gtm.js

49 ms

ScriptResource.axd

ScriptResource.axd

269 ms

Search-box.min.js

Search-box.min.js

62 ms

all.min.js

all.min.js

63 ms

c0f209f0-879d-0136-3dc1-06659b33d47c

c0f209f0-879d-0136-3dc1-06659b33d47c

25 ms

js

js

69 ms

analytics.js

analytics.js

40 ms

site-logo.png

site-logo.png

55 ms

bg-logo.png

bg-logo.png

54 ms

member-fdic.png

member-fdic.png

56 ms

equal_housing_lender_white.png

equal_housing_lender_white.png

55 ms

collect

collect

54 ms

pixel

pixel

336 ms

collect

collect

288 ms

cdpromo_7moand11mo__webheader94dd1e731dff6ddbb37cff0000940c19.jpg

cdpromo_7moand11mo__webheader94dd1e731dff6ddbb37cff0000940c19.jpg

321 ms

background.png

background.png

281 ms

cowboy-slider.png

cowboy-slider.png

394 ms

testimonial_webheader_background.jpg

testimonial_webheader_background.jpg

284 ms

savingselite_webbanner_background_2.jpg

savingselite_webbanner_background_2.jpg

282 ms

fgb_financialeducation.png

fgb_financialeducation.png

271 ms

onlinebanking_bluee2281c731dff6ddbb37cff0000940c19.png

onlinebanking_bluee2281c731dff6ddbb37cff0000940c19.png

314 ms

credit-debit_card_blue.png

credit-debit_card_blue.png

337 ms

autobooks_symbol.png

autobooks_symbol.png

335 ms

cardswap_blue.png

cardswap_blue.png

336 ms

pfm_blue.png

pfm_blue.png

337 ms

clickswitch_blue_icon.png

clickswitch_blue_icon.png

337 ms

cropped_community_involvement.png

cropped_community_involvement.png

339 ms

webpage.png

webpage.png

337 ms

investor_relations.jpg

investor_relations.jpg

353 ms

map-bg.jpg

map-bg.jpg

406 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilXs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilXs1Uj.woff

254 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClXs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClXs1Uj.woff

245 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVilXs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVilXs1Uj.woff

253 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5Xs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5Xs1Uj.woff

254 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5Xs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5Xs1Uj.woff

272 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVi5Xs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVi5Xs1Uj.woff

270 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4Gfy5Xs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4Gfy5Xs1Uj.woff

271 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

271 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

272 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

272 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

284 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

284 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

283 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

283 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

283 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

283 ms

pixel

pixel

55 ms

ga-audiences

ga-audiences

106 ms

five9-social-widget.min.js

five9-social-widget.min.js

281 ms

five9-social-widget.css

five9-social-widget.css

71 ms

slider-icon-arrow-prev.png

slider-icon-arrow-prev.png

28 ms

slider-icon-arrow-next.png

slider-icon-arrow-next.png

50 ms

fgb-center---web-friendly.jpg

fgb-center---web-friendly.jpg

107 ms

chat-small.png

chat-small.png

100 ms

minus-32.png

minus-32.png

153 ms

external-link-32.png

external-link-32.png

238 ms

Accessibility Review

fgb.net accessibility score

91

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

ARIA input fields do not have accessible names

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

SEO Factors

fgb.net SEO score

85

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

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 Fgb.net 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 Fgb.net 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

fgb.net

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