7.6 sec in total
3 sec
4.5 sec
161 ms
Click here to check amazing Princes Quay content. Otherwise, check out these important facts you probably never knew about princes-quay.co.uk
Visit princes-quay.co.ukWe analyzed Princes-quay.co.uk page load time and found that the first response time was 3 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
princes-quay.co.uk performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value2.9 s
80/100
25%
Value2.5 s
98/100
10%
Value80 ms
99/100
30%
Value0.029
100/100
15%
Value2.9 s
96/100
10%
2959 ms
86 ms
169 ms
173 ms
21 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 79% of them (48 requests) were addressed to the original Princes-quay.co.uk, 7% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Princes-quay.co.uk.
Page size can be reduced by 1.8 MB (67%)
2.6 MB
873.9 kB
In fact, the total size of Princes-quay.co.uk main page is 2.6 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. 55% of websites need less resources to load. CSS take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 47.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 47.1 kB or 81% of the original size.
Potential reduce by 5.8 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. Princes Quay images are well optimized though.
Potential reduce by 487.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 487.3 kB or 69% of the original size.
Potential reduce by 1.2 MB
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. Princes-quay.co.uk needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 90% of the original size.
Number of requests can be reduced by 39 (74%)
53
14
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Princes Quay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
princes-quay.co.uk
2959 ms
wp-emoji-release.min.js
86 ms
styles.css
169 ms
cff-style.css
173 ms
font-awesome.min.css
21 ms
style.css
188 ms
settings.css
174 ms
css
24 ms
css
37 ms
fontello.css
183 ms
jquery.fancybox.css
184 ms
slider.css
249 ms
bootstrap.min.css
335 ms
bootstrap-responsive.min.css
250 ms
style.css
342 ms
js_composer.css
468 ms
js_composer.css
431 ms
jquery.js
417 ms
jquery-migrate.min.js
331 ms
jquery.nailthumb.1.0.min.js
415 ms
jquery.themepunch.tools.min.js
515 ms
jquery.themepunch.revolution.min.js
529 ms
jquery.backstretch.min.js
512 ms
plugin.css
511 ms
jquery.form.min.js
534 ms
scripts.js
536 ms
cff-scripts.js
608 ms
TweenMax.min.js
666 ms
jquery.modernizr.min.js
611 ms
jquery.isotope.min.js
613 ms
jquery.easing.1.3.js
613 ms
jquery.fitvid.js
613 ms
bootstrap.min.js
660 ms
ddsmoothmenu.js
720 ms
jquery.fancybox.pack.js
722 ms
jquery.fancybox-media.js
724 ms
retina.js
725 ms
screen.js
742 ms
comment-reply.min.js
746 ms
js_composer_front.js
748 ms
analytics.js
11 ms
9chrfGYg_normal.jpg
81 ms
Cd7i7QiXEAEpJ4B.jpg
196 ms
pq-logo.png
330 ms
dummy.png
330 ms
realm_logo.png
330 ms
search.png
323 ms
collect
42 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
7 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
37 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
39 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
39 ms
counter.js
17 ms
t.php
106 ms
fontello-social.woff
239 ms
fontello.woff
376 ms
twitter_feed_icons_sprite.png
239 ms
loader.gif
86 ms
coloredbg.png
85 ms
revicons.woff
109 ms
the-quay.jpg
656 ms
princes-quay.co.uk 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.
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
princes-quay.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
princes-quay.co.uk SEO score
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 doesn't use legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Princes-quay.co.uk 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), while the claimed language is English. Our system also found out that Princes-quay.co.uk 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.
princes-quay.co.uk
Open Graph description is not detected on the main page of Princes Quay. 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: