Tools & Wizards About Us
regions.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

regions.com

Regions Bank | Checking, Savings, Mortgage, Loans & More | Regions Bank

Page Load Speed

37.4 sec in total

First Response

240 ms

Resources Loaded

23.9 sec

Page Rendered

13.3 sec

regions.com screenshot

About Website

Welcome to regions.com homepage info - get ready to check Regions best content for United States right away, or after learning these important things about regions.com

We offer a full spectrum of banking services including checking, savings, mortgages, loans and more. Visit us online or at your nearest branch location.

Visit regions.com

Key Findings

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

Performance Metrics

regions.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value20.6 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value2,220 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value20.1 s

2/100

10%

Network Requests Diagram

personal-banking

240 ms

com-regions-dotcom.min.css

148 ms

com-regions-dotcom-libs.min.js

883 ms

css

3192 ms

Bootstrap.js

3224 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 28% of them (18 requests) were addressed to the original Regions.com, 14% (9 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Ads.bridgetrack.com. The less responsive or slowest element that took the longest time to load (6 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (53%)

Content Size

2.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Regions.com main page is 2.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. 60% of websites need less resources to load. Images take 804.9 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 106.2 kB

  • Original 121.2 kB
  • After minification 80.7 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 40.5 kB, which is 33% 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 106.2 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 4.1 kB

  • Original 804.9 kB
  • After minification 800.9 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. Regions images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 427.0 kB

  • Original 575.7 kB
  • After minification 538.2 kB
  • After compression 148.7 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 427.0 kB or 74% of the original size.

CSS Optimization

-88%

Potential reduce by 663.6 kB

  • Original 752.0 kB
  • After minification 751.1 kB
  • After compression 88.4 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. Regions.com needs all CSS files to be minified and compressed as it can save up to 663.6 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (59%)

Requests Now

49

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

personal-banking

personal-banking

240 ms

com-regions-dotcom.min.css

com-regions-dotcom.min.css

148 ms

com-regions-dotcom-libs.min.js

com-regions-dotcom-libs.min.js

883 ms

css

css

3192 ms

Bootstrap.js

Bootstrap.js

3224 ms

com-regions-dotcom-application.min.js

com-regions-dotcom-application.min.js

3139 ms

platform.js

platform.js

4825 ms

com-regions-dotcom-print.min.css

com-regions-dotcom-print.min.css

607 ms

regions-logo.png

regions-logo.png

1046 ms

regions-logo.png

regions-logo.png

1044 ms

exit-notice-image

exit-notice-image

1045 ms

serverComponent.php

serverComponent.php

455 ms

2537 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

5019 ms

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

4809 ms

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

5094 ms

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

5018 ms

M2Jd71oPJhLKp0zdtTvoM0DauxaEVho0aInXGvhmB4k.ttf

M2Jd71oPJhLKp0zdtTvoM0DauxaEVho0aInXGvhmB4k.ttf

4770 ms

fpTVHK8qsXbIeTHTrnQH6Iue0YgdIF4L_q7PS4yTQOQ.ttf

fpTVHK8qsXbIeTHTrnQH6Iue0YgdIF4L_q7PS4yTQOQ.ttf

5056 ms

fpTVHK8qsXbIeTHTrnQH6Edtd7Dq2ZflsctMEexj2lw.ttf

fpTVHK8qsXbIeTHTrnQH6Edtd7Dq2ZflsctMEexj2lw.ttf

5993 ms

regions-icons-cfdc07a0645a1f57255d8c28d7d0f77d.woff

regions-icons-cfdc07a0645a1f57255d8c28d7d0f77d.woff

2972 ms

sdk.js

sdk.js

3970 ms

P-BA-NextStep-Beltrans-Pano.jpg

P-BA-NextStep-Beltrans-Pano.jpg

2841 ms

P-BA-NextStep-Beltrans-Pano.jpg

P-BA-NextStep-Beltrans-Pano.jpg

2840 ms

watercolor-gray.jpg

watercolor-gray.jpg

1903 ms

watercolor-insights.jpg

watercolor-insights.jpg

3511 ms

P-SI-MyGreenInsights-Pano.jpg

P-SI-MyGreenInsights-Pano.jpg

3510 ms

P-BA-CC-Consumer.jpg

P-BA-CC-Consumer.jpg

3511 ms

P-I-Regions_Insurance-Pano.jpg

P-I-Regions_Insurance-Pano.jpg

3593 ms

1034b0570824a7bbce6d8bead43ab9a9.js

1034b0570824a7bbce6d8bead43ab9a9.js

1810 ms

0AKsP294HTD-nvJgucYTaJ0EAVxt0G0biEntp43Qt6E.ttf

0AKsP294HTD-nvJgucYTaJ0EAVxt0G0biEntp43Qt6E.ttf

1325 ms

QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf

QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf

1354 ms

188c8d9de4a3dc179d6db15b8fc31fdd.js

188c8d9de4a3dc179d6db15b8fc31fdd.js

1271 ms

64993232

64993232

1487 ms

adServerESI.aspx

adServerESI.aspx

809 ms

mp_linkcode.js

mp_linkcode.js

436 ms

oo_engine.js

oo_engine.js

334 ms

_bt.js

_bt.js

872 ms

generic

generic

576 ms

mpel.js

mpel.js

880 ms

wtid.js

wtid.js

3598 ms

rtgt.asp

rtgt.asp

1161 ms

_btID.min.js

_btID.min.js

390 ms

1408 ms

_btID.asp

_btID.asp

2767 ms

mpel_storage.html

mpel_storage.html

33 ms

ca.gif

ca.gif

3341 ms

tr

tr

3686 ms

3000 ms

adsct

adsct

3685 ms

adsct

adsct

3853 ms

src=6125942;type=rmc;cat=regio0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1;num=1

src=6125942;type=rmc;cat=regio0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1;num=1

3291 ms

lb

lb

3096 ms

mpel

mpel

1206 ms

1503 ms

mpel_ssd.js

mpel_ssd.js

1422 ms

mpel_storage.html

mpel_storage.html

675 ms

855 ms

424146.gif

424146.gif

403 ms

448 ms

ecc

ecc

553 ms

dcs.gif

dcs.gif

575 ms

rightmedia

rightmedia

356 ms

rum

rum

95 ms

rum

rum

324 ms

Accessibility Review

regions.com accessibility score

100

Accessibility Issues

Best Practices

regions.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

regions.com 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

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Regions.com 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 Regions.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

regions.com

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