1.5 sec in total
52 ms
880 ms
612 ms
Click here to check amazing Peter Livingston content. Otherwise, check out these important facts you probably never knew about peterlivingston.com
Peter Livingston of Livingston Financial, a financial advisor in Mooresville/Lake Norman NC specializing in retirement and financial planning.
Visit peterlivingston.comWe analyzed Peterlivingston.com page load time and found that the first response time was 52 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
peterlivingston.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value16.7 s
0/100
25%
Value10.4 s
8/100
10%
Value1,050 ms
25/100
30%
Value0.119
85/100
15%
Value15.1 s
7/100
10%
52 ms
90 ms
178 ms
112 ms
68 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 8% of them (5 requests) were addressed to the original Peterlivingston.com, 62% (38 requests) were made to Static.fmgsuite.com and 7% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (457 ms) relates to the external source Dni.trumeasure.com.
Page size can be reduced by 183.4 kB (6%)
3.2 MB
3.0 MB
In fact, the total size of Peterlivingston.com main page is 3.2 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 3.0 MB which makes up the majority of the site volume.
Potential reduce by 46.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. This page needs HTML code to be minified as it can gain 10.8 kB, which is 18% 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 46.8 kB or 79% of the original size.
Potential reduce by 116.2 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. Peter Livingston images are well optimized though.
Potential reduce by 14.9 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 14.9 kB or 14% of the original size.
Potential reduce by 5.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. Peterlivingston.com needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 13% of the original size.
Number of requests can be reduced by 42 (76%)
55
13
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Peter Livingston. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
peterlivingston.com
52 ms
www.peterlivingston.com
90 ms
www.peterlivingston.com
178 ms
gtm.js
112 ms
global.css
68 ms
bootstrap.min.css
69 ms
font-awesome.min.css
89 ms
overrides.css
84 ms
css
101 ms
6.css
76 ms
6a.css
76 ms
advancedsections.css
75 ms
6ac.css
84 ms
global-asset-styles.css
83 ms
customtheme.css
81 ms
styles.css
103 ms
jquery.fancybox.css
84 ms
jquery.fancybox-buttons.css
84 ms
jquery.fancybox-thumbs.css
87 ms
jquery.min.js
88 ms
jquery-migrate-1.2.1.min.js
87 ms
4bd62c60-a2ee-0135-deec-06659b33d47c
90 ms
TMLoader.js
457 ms
js
335 ms
leadgen.js
86 ms
modernizr.custom.12650.js
86 ms
bootstrap.min.js
88 ms
jquery.validate.js
88 ms
jquery.validate.unobtrusive.js
88 ms
jquery.stellar.js
88 ms
video-scroll-play.js
116 ms
template006.js
88 ms
jquery.mousewheel-3.0.6.pack.js
89 ms
jquery.fancybox.pack.js
93 ms
jquery.fancybox-buttons.js
88 ms
jquery.fancybox-media.js
93 ms
jquery.fancybox-thumbs.js
91 ms
global.js
92 ms
contact.js
93 ms
popup-form.js
93 ms
dygraph-combined.js
90 ms
index.js
93 ms
global-asset-scripts.js
93 ms
css
41 ms
js
315 ms
js
268 ms
brokerCheck-bar-logo.png
192 ms
stress-test-button-DARK.png
369 ms
59501507
368 ms
fa0e99cc-4a33-4143-be2a-ee118dc81a00.png
159 ms
416d6903-f48a-41b6-9f81-e2e7e5aebfe7.jpg
129 ms
062-hero.jpg
130 ms
235-hero.jpg
128 ms
e643d8f8-7f7c-416b-bde1-492a0d802905.jpg
311 ms
99752a60-8e96-4520-82d2-fd4c19b6ad73.jpg
313 ms
6347ac99-b6fe-45a6-a5bf-b77e8c810be2.png
130 ms
loading.gif
130 ms
fontawesome-webfont.woff
128 ms
1Pt2g8TAX_SGgBGUi0tGOYEga5WOwnsS.ttf
212 ms
fbevents.js
143 ms
939190135-899505c78f318f29c0992ec2c744d7c0923c9e4a66de91ce3a3f53db0c88fc47-d
50 ms
peterlivingston.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 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
No form fields have multiple labels
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
peterlivingston.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
peterlivingston.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
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 Peterlivingston.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 Peterlivingston.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.
peterlivingston.com
Open Graph data is detected on the main page of Peter Livingston. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: