1.7 sec in total
303 ms
1.3 sec
160 ms
Click here to check amazing Shop Prince Squash content. Otherwise, check out these important facts you probably never knew about shop.princesquash.com
The official distributor of Prince squash equipment in the US.
Visit shop.princesquash.comWe analyzed Shop.princesquash.com page load time and found that the first response time was 303 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
shop.princesquash.com performance score
303 ms
277 ms
94 ms
93 ms
95 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 99% of them (67 requests) were addressed to the original Shop.princesquash.com, 1% (1 request) were made to Princesquash.com. The less responsive or slowest element that took the longest time to load (531 ms) relates to the external source Princesquash.com.
Page size can be reduced by 773.6 kB (51%)
1.5 MB
738.0 kB
In fact, the total size of Shop.princesquash.com main page is 1.5 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 737.6 kB which makes up the majority of the site volume.
Potential reduce by 36.3 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 11.1 kB, which is 26% 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 36.3 kB or 84% of the original size.
Potential reduce by 118.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. Obviously, Shop Prince Squash needs image optimization as it can save up to 118.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 462.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 462.9 kB or 83% of the original size.
Potential reduce by 156.3 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. Shop.princesquash.com needs all CSS files to be minified and compressed as it can save up to 156.3 kB or 89% of the original size.
Number of requests can be reduced by 34 (56%)
61
27
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shop Prince Squash. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
shop.princesquash.com
303 ms
jQuery-1.7.2.min.js
277 ms
jquery.watermark.min.js
94 ms
SearchWatermark.js
93 ms
Default.css
95 ms
WebResource.axd
185 ms
ScriptResource.axd
140 ms
ScriptResource.axd
232 ms
ScriptResource.axd
154 ms
embedInCatalog.js
95 ms
Default.css
48 ms
ContentReplacement.css
48 ms
_Default.css
141 ms
Primitives.css
48 ms
Buttons.css
50 ms
jquery-nav.css
51 ms
PageHeader.css
50 ms
HeaderBanner.css
49 ms
NavCategoryTreeView.css
95 ms
NavProductTagging.css
94 ms
PageSearchForm.css
93 ms
StoreSelector.css
93 ms
ProductTile.css
94 ms
_LoginPage.css
144 ms
_Category.css
145 ms
_Checkout.css
145 ms
_ShoppingCart.css
144 ms
_Product.css
146 ms
Home.css
183 ms
ProductSpecificationsTab.css
185 ms
Specials.css
186 ms
EmailAFriend.css
183 ms
_Style.css
186 ms
_Style.css
183 ms
LoginPageBlock.css
88 ms
NavCategoryDropDown.css
86 ms
NavCategoryTreeView.css
87 ms
HomeBanner.jpg
531 ms
logo_291113030051.png
49 ms
waitt-company.png
50 ms
Products.jpg
95 ms
Athletes.jpg
95 ms
inside-prince.jpg
94 ms
sign-up.jpg
96 ms
sign-up.png
95 ms
SearchMagnifyingGlassIcon.png
92 ms
WebResource.axd
144 ms
ProRebel950_Front-13579.jpg
140 ms
ProTour850_Front-13580.jpg
143 ms
ProBeast750-PB_Front-13583.jpg
139 ms
TeamPeterNicol700_Front-13600.jpg
142 ms
facebook-icon2.png
142 ms
youtube-icon2.png
189 ms
PageHeaderShadow.png
149 ms
thinbar.png
153 ms
product-shadow.png
145 ms
category-product-arrow.png
145 ms
footer-background.jpg
144 ms
FunctionPro-Book-webfont.woff
186 ms
FunctionPro-Medium-webfont.woff
189 ms
FunctionPro-Light-webfont.woff
191 ms
FunctionPro-Demi-webfont.woff
189 ms
FunctionPro-Bold-webfont.woff
190 ms
FranchiseBoldHinted.woff
182 ms
ContentProxy.ashx
224 ms
WebResource.axd
215 ms
WebResource.axd
218 ms
WebResource.axd
225 ms
shop.princesquash.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shop.princesquash.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Shop.princesquash.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.
shop.princesquash.com
Open Graph description is not detected on the main page of Shop Prince Squash. 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: