Tools & Wizards About Us
fidelityfirst.net screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

fidelityfirst.net

Mortgages | Annapolis, MD - Fidelity First

Page Load Speed

1.3 sec in total

First Response

311 ms

Resources Loaded

870 ms

Page Rendered

137 ms

fidelityfirst.net screenshot

About Website

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

Overcome your imperfect credit and move into the home of your dreams with one of our mortgages in Annapolis, MD. Refinance your mortgage with a fixed-rate loan.

Visit fidelityfirst.net

Key Findings

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

Performance Metrics

fidelityfirst.net performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

fidelityfirst.net

311 ms

__utm.js

109 ms

index-rollovers.js

56 ms

fidelityfirst-stylesheet.css

57 ms

AC_RunActiveContent.js

59 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 89% of them (55 requests) were addressed to the original Fidelityfirst.net, 6% (4 requests) were made to Google-analytics.com and 2% (1 request) were made to Zillow.com. The less responsive or slowest element that took the longest time to load (375 ms) belongs to the original domain Fidelityfirst.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.0 kB (41%)

Content Size

48.5 kB

After Optimization

28.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Fidelityfirst.net main page is 48.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. 20% of websites need less resources to load. Javascripts take 24.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 17.5 kB

  • Original 22.6 kB
  • After minification 19.8 kB
  • After compression 5.1 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 2.8 kB, which is 12% 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 17.5 kB or 78% of the original size.

JavaScript Optimization

-4%

Potential reduce by 1.0 kB

  • Original 24.0 kB
  • After minification 24.0 kB
  • After compression 23.0 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.

CSS Optimization

-77%

Potential reduce by 1.5 kB

  • Original 1.9 kB
  • After minification 1.5 kB
  • After compression 452 B

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. Fidelityfirst.net needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (23%)

Requests Now

60

After Optimization

46

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fidelityfirst.net

fidelityfirst.net

311 ms

__utm.js

__utm.js

109 ms

index-rollovers.js

index-rollovers.js

56 ms

fidelityfirst-stylesheet.css

fidelityfirst-stylesheet.css

57 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

59 ms

ga.js

ga.js

44 ms

bdg_lender.gif

bdg_lender.gif

162 ms

__utm.gif

__utm.gif

75 ms

questions_on.jpg

questions_on.jpg

82 ms

questions_off.jpg

questions_off.jpg

81 ms

calculators_on.jpg

calculators_on.jpg

85 ms

calculators_off.jpg

calculators_off.jpg

85 ms

about_on.jpg

about_on.jpg

56 ms

about_off.jpg

about_off.jpg

111 ms

security_on.jpg

security_on.jpg

136 ms

security_off.jpg

security_off.jpg

151 ms

newpurchase_on.jpg

newpurchase_on.jpg

141 ms

newpurchase_off.jpg

newpurchase_off.jpg

158 ms

homeequity_on.jpg

homeequity_on.jpg

135 ms

homeequity_off.jpg

homeequity_off.jpg

170 ms

refinance_on.jpg

refinance_on.jpg

189 ms

refinance_off.jpg

refinance_off.jpg

189 ms

contactus_on.jpg

contactus_on.jpg

199 ms

contactus_off.jpg

contactus_off.jpg

205 ms

home_int_on.jpg

home_int_on.jpg

211 ms

home_int_off.jpg

home_int_off.jpg

222 ms

newpurchase_int_on.jpg

newpurchase_int_on.jpg

243 ms

newpurchase_int_off.jpg

newpurchase_int_off.jpg

243 ms

homeequity_int_on.jpg

homeequity_int_on.jpg

252 ms

homeequity_int_off.jpg

homeequity_int_off.jpg

259 ms

refinance_int_on.jpg

refinance_int_on.jpg

263 ms

refinance_int_off.jpg

refinance_int_off.jpg

275 ms

staffbios_int_on.jpg

staffbios_int_on.jpg

297 ms

staffbios_int_off.jpg

staffbios_int_off.jpg

298 ms

reversemortgage_int_on.jpg

reversemortgage_int_on.jpg

305 ms

reversemortgage_int_off.jpg

reversemortgage_int_off.jpg

312 ms

contactus_short_int_on.jpg

contactus_short_int_on.jpg

317 ms

contactus_short_int_off.jpg

contactus_short_int_off.jpg

329 ms

fidelityfirst_logo.jpg

fidelityfirst_logo.jpg

375 ms

twitter_icon.jpg

twitter_icon.jpg

361 ms

fb_icon.jpg

fb_icon.jpg

359 ms

img_indexnumber.jpg

img_indexnumber.jpg

366 ms

urchin.js

urchin.js

25 ms

top-divider.gif

top-divider.gif

370 ms

__utm.gif

__utm.gif

13 ms

__utm.gif

__utm.gif

6 ms

img_indexbtm1.jpg

img_indexbtm1.jpg

335 ms

img_indexbullet.gif

img_indexbullet.gif

348 ms

reversemortgage.jpg

reversemortgage.jpg

343 ms

commercial.jpg

commercial.jpg

348 ms

meetstaff.jpg

meetstaff.jpg

353 ms

improve-credit.gif

improve-credit.gif

355 ms

predatory-loans.gif

predatory-loans.gif

334 ms

img-underline.gif

img-underline.gif

340 ms

mamp_sm.gif

mamp_sm.gif

342 ms

namb_sm.gif

namb_sm.gif

342 ms

md_coc_sm.gif

md_coc_sm.gif

340 ms

dividerShort.gif

dividerShort.gif

338 ms

eschool.jpg

eschool.jpg

330 ms

bbbsealh1US.gif

bbbsealh1US.gif

339 ms

vTracker_v2.asp

vTracker_v2.asp

9 ms

vTracker_v2.asp

vTracker_v2.asp

27 ms

Accessibility Review

fidelityfirst.net accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fidelityfirst.net SEO score

98

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fidelityfirst.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fidelityfirst.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

fidelityfirst.net

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