2.6 sec in total
35 ms
2.1 sec
460 ms
Visit firstutahbank.com now to see the best up-to-date First Utah Bank content for United States and also check out these interesting facts you probably never knew about firstutahbank.com
First Utah Bank has been the leading community bank of Salt Lake City with top personal and business banking solutions since 1978. Get in touch with us for any inquiries.
Visit firstutahbank.comWe analyzed Firstutahbank.com page load time and found that the first response time was 35 ms and then it took 2.5 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.
firstutahbank.com performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value10.2 s
1/100
25%
Value14.7 s
1/100
10%
Value760 ms
39/100
30%
Value0
100/100
15%
Value20.1 s
2/100
10%
35 ms
140 ms
179 ms
97 ms
272 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 58% of them (37 requests) were addressed to the original Firstutahbank.com, 6% (4 requests) were made to Web15.secureinternetbank.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Firstutahbank.com.
Page size can be reduced by 269.2 kB (4%)
6.9 MB
6.6 MB
In fact, the total size of Firstutahbank.com main page is 6.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. 70% of websites need less resources to load. Images take 6.7 MB which makes up the majority of the site volume.
Potential reduce by 48.8 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 48.8 kB or 81% of the original size.
Potential reduce by 214.3 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. First Utah Bank images are well optimized though.
Potential reduce by 4.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 1.8 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. Firstutahbank.com 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 First Utah Bank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
firstutahbank.com
35 ms
gtm.js
140 ms
js
179 ms
fbevents.js
97 ms
slick.css
272 ms
slick-theme.css
299 ms
jquery.modal.min.css
168 ms
font-awesome.min.css
173 ms
css
167 ms
hamburgers.css
299 ms
style.css
302 ms
s5-syndication.css
296 ms
styles.css
295 ms
styles.min.css
348 ms
jquery.min.js
500 ms
jquery-migrate.min.js
352 ms
s5-syndication.js
354 ms
remoteLoginLoad
350 ms
Remoteloginload
387 ms
index.js
350 ms
index.js
351 ms
api.js
167 ms
regenerator-runtime.min.js
353 ms
wp-polyfill.min.js
390 ms
index.js
390 ms
jquery.min.js
161 ms
jquery-ui.js
186 ms
imagesloaded.pkgd.min.js
199 ms
jquery.modal.min.js
202 ms
slick.min.js
444 ms
jquery.easytabs.js
390 ms
functions.js
388 ms
1075299935965262
102 ms
js
44 ms
analytics.js
64 ms
collect
94 ms
wp-emoji-release.min.js
104 ms
FUB_Logo_Final_Reversed-Square.png
290 ms
app-store-badge.png
118 ms
google-play-badge.png
118 ms
Business-Relationship-Shaking-Hands.jpg
318 ms
foot-icon.png
118 ms
remoteLoginPost
116 ms
remoteLoginPost
117 ms
MobileBankingHomePage-e1611086797852.jpg
909 ms
ExternalHeader1.jpg
1005 ms
AlertsHeader1.jpg
686 ms
BusinessCreditCard.jpg
1008 ms
discovery-1.jpg
876 ms
MobileBankingBUSINESSPage-e1611086767283.jpg
561 ms
FoodBankMobilePantry.jpg
937 ms
BentonSans-Regular.woff
635 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7jujVj9w.woff
169 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo3cOWxw.woff
199 ms
BentonSans-Bold.woff
690 ms
fontawesome-webfont.woff
63 ms
wlpygwjKBV1pqhND-ZQW-WVlaiBW.woff
220 ms
wlp_gwjKBV1pqhv43Ic7225P.woff
221 ms
BentonSans-Light.woff
747 ms
wdp.js
216 ms
recaptcha__en.js
205 ms
ajax-loader.gif
636 ms
La-Quinta-La-Verkin.jpg
763 ms
logo.js
11 ms
firstutahbank.com 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
firstutahbank.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
firstutahbank.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Firstutahbank.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 Firstutahbank.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.
firstutahbank.com
Open Graph data is detected on the main page of First Utah Bank. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: