3.8 sec in total
675 ms
2.8 sec
367 ms
Visit pery.com now to see the best up-to-date Pery content for United States and also check out these interesting facts you probably never knew about pery.com
Perry Ellis International
Visit pery.comWe analyzed Pery.com page load time and found that the first response time was 675 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pery.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value103.4 s
0/100
25%
Value37.3 s
0/100
10%
Value90 ms
99/100
30%
Value0.155
74/100
15%
Value97.2 s
0/100
10%
675 ms
517 ms
389 ms
392 ms
531 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 80% of them (73 requests) were addressed to the original Pery.com, 14% (13 requests) were made to Investor.pery.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Pery.com.
Page size can be reduced by 1.4 MB (13%)
10.7 MB
9.2 MB
In fact, the total size of Pery.com main page is 10.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. 45% of websites need less resources to load. Images take 9.7 MB which makes up the majority of the site volume.
Potential reduce by 28.8 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 7.1 kB, which is 22% 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 28.8 kB or 87% of the original size.
Potential reduce by 580.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. Pery images are well optimized though.
Potential reduce by 541.2 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 541.2 kB or 81% of the original size.
Potential reduce by 271.7 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. Pery.com needs all CSS files to be minified and compressed as it can save up to 271.7 kB or 87% of the original size.
Number of requests can be reduced by 35 (41%)
86
51
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pery. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
pery.com
675 ms
Foundation.css
517 ms
Site.css
389 ms
font-awesome.min.css
392 ms
foundation-icons.css
531 ms
analytics.js
24 ms
modernizr-2.6.2.js
509 ms
jquery-1.10.2.js
297 ms
fastclick.js
228 ms
foundation.js
228 ms
foundation.abide.js
260 ms
foundation.accordion.js
251 ms
foundation.alert.js
254 ms
foundation.clearing.js
330 ms
foundation.dropdown.js
331 ms
foundation.equalizer.js
330 ms
foundation.interchange.js
340 ms
foundation.joyride.js
355 ms
foundation.magellan.js
356 ms
foundation.offcanvas.js
349 ms
foundation.orbit.js
371 ms
foundation.reveal.js
408 ms
foundation.slider.js
406 ms
foundation.tab.js
408 ms
foundation.tooltip.js
427 ms
foundation.topbar.js
441 ms
ga.js
435 ms
Header.js
458 ms
Slideshow.js
458 ms
quote_include.cfm
139 ms
releases_include.cfm
151 ms
logo_black.png
323 ms
perryellis.jpg
1000 ms
axist.jpg
465 ms
benhogan.jpg
1310 ms
callaway.jpg
506 ms
cubavera.jpg
609 ms
grandslam.jpg
758 ms
havanera.jpg
748 ms
jacknicklaus.jpg
821 ms
jag.jpg
973 ms
jantzen.jpg
962 ms
johnhenry.jpg
1027 ms
laundry.jpg
1203 ms
nikeswim.jpg
1649 ms
originalpenguin.jpg
1184 ms
brandon_re-webfont.ttf
1270 ms
fontawesome-webfont.woff
1225 ms
foundation-icons.woff
1272 ms
peony.jpg
1300 ms
pgatour.jpg
1661 ms
proplayer.jpg
1264 ms
rafaella.jpg
1420 ms
savane.jpg
1432 ms
2631BF_2_0.woff
103 ms
perryellis.png
1457 ms
default.css
62 ms
wsh_default.css
67 ms
wsh_script_absent.css
43 ms
sh_scripts.js
69 ms
jquery.min.js
39 ms
frame.js
43 ms
exLinks.js
84 ms
s_code_baseline_dev_v3.js
199 ms
axist.png
1459 ms
benhogan.png
1485 ms
callaway.png
1503 ms
cubavera.png
1504 ms
grandslam.png
1489 ms
havanera.png
1496 ms
jacknicklaus.png
1513 ms
icon_rss.gif
105 ms
jag.png
1497 ms
jantzen.png
1502 ms
collect
69 ms
johnhenry.png
1505 ms
quote_include.cfm
99 ms
laundry.png
1443 ms
nikeswim.png
1455 ms
originalpenguin.png
1471 ms
s87378751046489
9 ms
wsh_print.css
47 ms
trackpage.aspx
54 ms
peony.png
1328 ms
pgatour.png
1306 ms
proplayer.png
1217 ms
rafaella.png
1073 ms
savane.png
1070 ms
thumb1.jpg
1030 ms
thumb2.jpg
912 ms
thumb3.jpg
912 ms
pery.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
pery.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
pery.com SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pery.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 Pery.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.
pery.com
Open Graph description is not detected on the main page of Pery. 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: