7.6 sec in total
1.3 sec
5.9 sec
414 ms
Welcome to grahamnicholls.com homepage info - get ready to check Grahamnicholls best content for Estonia right away, or after learning these important things about grahamnicholls.com
Author and specialist on Astral Projection and Out-of-Body Experiences
Visit grahamnicholls.comWe analyzed Grahamnicholls.com page load time and found that the first response time was 1.3 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
grahamnicholls.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value19.9 s
0/100
25%
Value8.8 s
16/100
10%
Value3,690 ms
1/100
30%
Value0.09
92/100
15%
Value14.8 s
8/100
10%
1262 ms
462 ms
372 ms
389 ms
387 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 92% of them (78 requests) were addressed to the original Grahamnicholls.com, 2% (2 requests) were made to Apis.google.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Grahamnicholls.com.
Page size can be reduced by 722.7 kB (24%)
3.0 MB
2.3 MB
In fact, the total size of Grahamnicholls.com main page is 3.0 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. 40% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 35.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. 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 35.1 kB or 76% of the original size.
Potential reduce by 133.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. Grahamnicholls images are well optimized though.
Potential reduce by 438.1 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 438.1 kB or 71% of the original size.
Potential reduce by 115.6 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. Grahamnicholls.com needs all CSS files to be minified and compressed as it can save up to 115.6 kB or 71% of the original size.
Number of requests can be reduced by 55 (65%)
84
29
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grahamnicholls. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
grahamnicholls.com
1262 ms
wp-emoji-release.min.js
462 ms
nextgen_gallery_related_images.css
372 ms
pushquote.css
389 ms
audiorecorder.css
387 ms
miniplayer.css
393 ms
style.css
579 ms
dashicons.min.css
901 ms
thickbox.css
634 ms
front.css
622 ms
social_widget.css
525 ms
wpcf.css
578 ms
jquery-ui.css
904 ms
custom-contact-forms-standards.css
731 ms
custom-contact-forms.css
749 ms
addtoany.min.css
788 ms
ajax.js
827 ms
jquery.js
1498 ms
jquery-migrate.min.js
964 ms
persist.js
1202 ms
store.js
1016 ms
ngg_store.js
1028 ms
custom-contact-forms-datepicker.js
1125 ms
jquery.tools.min.js
1454 ms
custom-contact-forms.js
1220 ms
lightbox_context.js
1235 ms
jsapi
19 ms
amazon_linker.min.js
1361 ms
audio-player.js
1623 ms
jd.gallery.css
1459 ms
mootools-1.2.4-core-jm.js
1883 ms
mootools-1.2.4.4-more.js
1565 ms
jd.gallery_1_2_4_4.js
1872 ms
jd.gallery.transitions_1_2_4_4.js
1678 ms
wide-rounded.css
1627 ms
plusone.js
34 ms
pushquote.js
1585 ms
jquery.jplayer.js
2142 ms
jquery.mb.miniPlayer.js
1806 ms
core.min.js
1700 ms
datepicker.min.js
1890 ms
thickbox.js
1870 ms
hoverIntent.min.js
1855 ms
superfish.min.js
1810 ms
superfish.args.min.js
1719 ms
superfish.compat.min.js
1853 ms
ga.js
64 ms
cb=gapi.loaded_0
76 ms
bg.png
876 ms
logo.png
851 ms
nav.png
495 ms
sidebar-bottom.png
496 ms
sidebar-header.png
617 ms
loading-bar-black.gif
644 ms
navigator-box-alone.jpg
1066 ms
graham-youtube-4-13.png
1639 ms
sleepresearch.jpg
1552 ms
Svalbard.png
2010 ms
swedenborg.jpg
1592 ms
cbb-cover.jpg
2462 ms
Infra-liminal-box-1-dynamic.jpg
2036 ms
handsopen-270x150.jpg
1833 ms
IRVA-2014-1-web-270x150.jpg
1994 ms
Infra-liminallogo1-270x150.jpg
1906 ms
NOBEadgnicholls-270x150.jpg
2161 ms
Avenues_books1-270x150.jpg
2236 ms
enews-sidebar.png
2193 ms
facebook.png
2254 ms
googleplus.png
2260 ms
twitter.png
2359 ms
linkedin.png
2400 ms
youtube.png
2457 ms
rss.png
2453 ms
email.png
2477 ms
page.js
28 ms
sleepresearch-150x150.jpg
2540 ms
__utm.gif
26 ms
Svalbard-150x150.png
2804 ms
IMG_0454-e1410604912298-150x150.jpg
2593 ms
Infra-liminal-box-1-web-150x150.jpg
2492 ms
footer.png
2453 ms
loadingAnimation.gif
2292 ms
fleche1.png
2291 ms
fleche2.png
2393 ms
36 ms
grahamnicholls.com accessibility score
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
<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
grahamnicholls.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
Missing source maps for large first-party JavaScript
grahamnicholls.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
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grahamnicholls.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 Grahamnicholls.com 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.
grahamnicholls.com
Open Graph description is not detected on the main page of Grahamnicholls. 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: