11.3 sec in total
2.3 sec
8.6 sec
441 ms
Click here to check amazing Greg Staunton content. Otherwise, check out these important facts you probably never knew about greg-staunton.com
I specialize in Enterprise size Eloqua implementations. I have a proven track record implementing on behalf of consultancy firms such as Deloitte and PwC.
Visit greg-staunton.comWe analyzed Greg-staunton.com page load time and found that the first response time was 2.3 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
greg-staunton.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value14.8 s
0/100
25%
Value15.1 s
1/100
10%
Value2,460 ms
5/100
30%
Value0.021
100/100
15%
Value17.7 s
4/100
10%
2279 ms
236 ms
291 ms
306 ms
34 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 39% of them (41 requests) were addressed to the original Greg-staunton.com, 30% (31 requests) were made to I0.wp.com and 10% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source I0.wp.com.
Page size can be reduced by 313.7 kB (26%)
1.2 MB
871.9 kB
In fact, the total size of Greg-staunton.com main page is 1.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. 65% of websites need less resources to load. Images take 473.6 kB which makes up the majority of the site volume.
Potential reduce by 233.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 233.0 kB or 84% of the original size.
Potential reduce by 18.1 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. Greg Staunton images are well optimized though.
Potential reduce by 55.5 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 55.5 kB or 14% of the original size.
Potential reduce by 7.2 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. Greg-staunton.com needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 19% of the original size.
Number of requests can be reduced by 53 (58%)
91
38
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greg Staunton. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
greg-staunton.com
2279 ms
icons.min.css
236 ms
agsdi-icons.min.css
291 ms
sbi-styles.min.css
306 ms
mediaelementplayer-legacy.min.css
34 ms
wp-mediaelement.min.css
39 ms
main.min.css
318 ms
style-block-editor.css
332 ms
cookie-law-info-public.css
336 ms
cookie-law-info-gdpr.css
381 ms
front.min.css
391 ms
slick.min.css
412 ms
magnific-popup.min.css
428 ms
frontend.css
446 ms
css
57 ms
style.min.css
342 ms
jquery.min.js
6 ms
jquery-migrate.min.js
6 ms
icons.min.js
393 ms
agsdi-icons.min.js
479 ms
clipboardv201.min.js
489 ms
prism.js
515 ms
manually-start-prism.js
486 ms
code-snippet-dm-public.js
486 ms
cookie-law-info-public.js
509 ms
seo-automated-link-building.js
590 ms
ie-compat.min.js
595 ms
js
67 ms
cookie-law-info-table.css
692 ms
run_prettify.js
693 ms
43618510.js
121 ms
front.min.js
699 ms
slick.min.js
748 ms
jquery.magnific-popup.min.js
747 ms
react.min.js
4 ms
react-dom.min.js
12 ms
frontend.js
747 ms
scripts.min.js
948 ms
jquery.fitvids.js
747 ms
jquery.mobile.js
871 ms
easypiechart.js
856 ms
salvattore.js
858 ms
frontend-bundle.min.js
859 ms
common.js
861 ms
e-202447.js
33 ms
mediaelement-and-player.min.js
10 ms
mediaelement-migrate.min.js
23 ms
wp-mediaelement.min.js
23 ms
sa.js
623 ms
heap-4087839225.js
248 ms
quant.js
184 ms
eloqua-implementation.png
734 ms
sbi-sprite.png
383 ms
eloqua-small.png
210 ms
eloqua-contractor-scaled.jpg
786 ms
logo-cookieyes.svg
370 ms
eloqua-training.png
242 ms
eloqua-campaign-delivery.png
715 ms
eloqua-custom-development.png
232 ms
eloqua-integration.png
718 ms
eloqua-sfdc-integration-define.png
241 ms
aberdeen-eloqua-1.png
774 ms
bt-eloqua-1.png
950 ms
cigna-eloqua-1.png
776 ms
deloitte-eloqua.png
1191 ms
deltek-eloqua.png
1223 ms
dnvgl-eloqua.png
1262 ms
dunnhumby-eloqua.png
1320 ms
Eurostar-eloqua.png
1318 ms
hmh-eloqua.png
1493 ms
lexisnexis-eloqua.png
1802 ms
oracle-eloqua.png
1730 ms
palo-alto-eloqua.png
1813 ms
pwc-eloqua.png
1810 ms
returnpath-eloqua-1.png
1922 ms
rockwell-eloqua-1.png
2037 ms
Rolls-Royce-eloqua.png
2375 ms
sage-eloqua.png
2259 ms
servicenow-eloqua-1.png
2384 ms
sse-eloqua.png
2317 ms
talktalk-eloqua.png
2634 ms
vmware-eloqua.png
2520 ms
vodafone-eloqua.png
2841 ms
eloqua-lead-scoring-1-scaled.jpg
2364 ms
keepcoding-lVF2HLzjopw-unsplash-scaled.jpg
2414 ms
wylly-suhendra-Swk4G_xi_uM-unsplash-scaled.jpg
3402 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
105 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
138 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
164 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
162 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
150 ms
modules.woff
382 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf
163 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf
161 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf
160 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf
164 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVc.ttf
165 ms
load.sumome.com
94 ms
prettify.css
249 ms
sumome.js
4 ms
banner.js
225 ms
43618510.js
225 ms
collectedforms.js
166 ms
h
75 ms
greg-staunton.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.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
greg-staunton.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
greg-staunton.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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greg-staunton.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 Greg-staunton.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.
greg-staunton.com
Open Graph description is not detected on the main page of Greg Staunton. 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: