11.3 sec in total
3.8 sec
7.1 sec
408 ms
Visit patrickjames.com now to see the best up-to-date Patrick James content for United States and also check out these interesting facts you probably never knew about patrickjames.com
A purveyor of fine menswear since 1962, Patrick James delivers impeccable classic looks that keep your wardrobe moving forward in a confident, modern direction. Shop our catalog for luxe, laidback sel...
Visit patrickjames.comWe analyzed Patrickjames.com page load time and found that the first response time was 3.8 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Patrickjames.com rating and web reputation
patrickjames.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value35.1 s
0/100
25%
Value6.9 s
33/100
10%
Value1,890 ms
9/100
30%
Value0.004
100/100
15%
Value45.5 s
0/100
10%
3816 ms
2943 ms
67 ms
3260 ms
3068 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 66% of them (61 requests) were addressed to the original Patrickjames.com, 14% (13 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Patrickjames.com.
Page size can be reduced by 584.1 kB (34%)
1.7 MB
1.2 MB
In fact, the total size of Patrickjames.com main page is 1.7 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. Images take 962.0 kB which makes up the majority of the site volume.
Potential reduce by 43.7 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 43.7 kB or 74% of the original size.
Potential reduce by 27.3 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. Patrick James images are well optimized though.
Potential reduce by 351.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 351.9 kB or 67% of the original size.
Potential reduce by 161.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. Patrickjames.com needs all CSS files to be minified and compressed as it can save up to 161.2 kB or 86% of the original size.
Number of requests can be reduced by 55 (71%)
78
23
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Patrick James. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
Default.aspx
3816 ms
Skin022.css
2943 ms
css
67 ms
bootstrap.min.css
3260 ms
bootstrap-override.css
3068 ms
jquery.min.js
50 ms
bootstrap.min.js
3045 ms
WebResource.axd
2951 ms
ScriptResource.axd
1158 ms
ScriptResource.axd
1277 ms
ScriptResource.axd
1399 ms
ScriptResource.axd
1517 ms
ScriptResource.axd
1638 ms
ScriptResource.axd
1757 ms
ScriptResource.axd
1877 ms
ScriptResource.axd
2246 ms
ScriptResource.axd
2372 ms
ScriptResource.axd
2496 ms
ScriptResource.axd
2613 ms
ScriptResource.axd
2623 ms
ScriptResource.axd
2731 ms
ScriptResource.axd
2732 ms
ScriptResource.axd
2638 ms
ScriptResource.axd
2669 ms
ScriptResource.axd
2684 ms
ScriptResource.axd
2684 ms
ScriptResource.axd
2725 ms
ScriptResource.axd
2728 ms
ScriptResource.axd
2743 ms
ScriptResource.axd
2742 ms
ScriptResource.axd
2743 ms
resxclsa.js
2357 ms
css
18 ms
css
30 ms
ga.js
30 ms
b.min.js
16 ms
phone.png
48 ms
phonewhite.png
69 ms
cart.png
474 ms
cartwhite.png
76 ms
PatrickJamesLogo.png
78 ms
chat2.png
81 ms
search.png
101 ms
catalog-quote.png
149 ms
PJ-Essentials.jpg
160 ms
Team-Shop.jpg
161 ms
PJ-Rewards.png
220 ms
Spring-Catalog-D1.png
341 ms
VerisignSeal.jpg
193 ms
__utm.gif
12 ms
webfont.js
14 ms
gtm.js
45 ms
91f6f2565abe56145a4b70fcc1b51b2e.js
45 ms
HeaderBackground3.gif
61 ms
bg-texture13.png
36 ms
Hero.jpg
341 ms
Sub-1.jpg
329 ms
Sub-2.jpg
537 ms
Resonance.aspx
230 ms
css
55 ms
FooterBackground.png
62 ms
emailicon.png
475 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
95 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
135 ms
4cKlrioa77J2iqTqBgkRWg.ttf
136 ms
2NBgzUtEeyB-Xtpr9bm1Cczai8e7xzqnKiVb1EwOy0E.ttf
146 ms
UC3ZEjagJi85gF9qFaBgIETamuWRjOQSPxoOXgdYd7c.ttf
145 ms
UC3ZEjagJi85gF9qFaBgIA0DQt4XpTxu2mZR8niJHm4.ttf
145 ms
__utm.gif
46 ms
avmws_1012231.js
473 ms
C1AEE05D6F16B7.js
85 ms
Resonance.aspx
149 ms
Hm1qjDlZpOdVXoa-QGE7_w.ttf
87 ms
L74890HNVnUypqWjqGUt1aCWcynf_cDxXwCLxiixG1c.ttf
76 ms
jquery.min.js
51 ms
config.js
15 ms
6467784181f6b5fa82eee2fa002285ed.js
38 ms
591f5bd1c76464c93da9ca6eb8de5c68.js
14 ms
10433_c.jpg
236 ms
10406_c.jpg
177 ms
10419_c.jpg
152 ms
10450_c.jpg
215 ms
8576_c.jpg
225 ms
8770_c.jpg
340 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
32 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
49 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
60 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
65 ms
4cKlrioa77J2iqTqBgkRWg.ttf
64 ms
10476_c.jpg
321 ms
10361_c.jpg
367 ms
8595_c.jpg
399 ms
10493_c.jpg
368 ms
patrickjames.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
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
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.
patrickjames.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
patrickjames.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Patrickjames.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 Patrickjames.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.
patrickjames.com
Open Graph description is not detected on the main page of Patrick James. 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: