1.3 sec in total
103 ms
706 ms
476 ms
Welcome to prex.com homepage info - get ready to check Prex best content for United States right away, or after learning these important things about prex.com
Princeton Record Exchange is one of the leading independent record stores in the world. We’ve been buying and selling music and movies since 1980. We are located in historic downtown Princeton, NJ, ab...
Visit prex.comWe analyzed Prex.com page load time and found that the first response time was 103 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
prex.com performance score
name
value
score
weighting
Value1.7 s
93/100
10%
Value2.3 s
93/100
25%
Value1.7 s
100/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value2.0 s
99/100
10%
103 ms
75 ms
26 ms
30 ms
35 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 76% of them (37 requests) were addressed to the original Prex.com, 10% (5 requests) were made to Google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (191 ms) belongs to the original domain Prex.com.
Page size can be reduced by 533.9 kB (68%)
781.6 kB
247.7 kB
In fact, the total size of Prex.com main page is 781.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 326.4 kB which makes up the majority of the site volume.
Potential reduce by 95.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 24.4 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 95.8 kB or 86% of the original size.
Potential reduce by 9.0 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. Prex images are well optimized though.
Potential reduce by 217.5 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 217.5 kB or 67% of the original size.
Potential reduce by 211.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. Prex.com needs all CSS files to be minified and compressed as it can save up to 211.6 kB or 83% of the original size.
Number of requests can be reduced by 26 (55%)
47
21
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
prex.com
103 ms
www.prex.com
75 ms
prex.js
26 ms
page_menu.js
30 ms
mm_menu.js
35 ms
AC_RunActiveContent.js
33 ms
hover.js
32 ms
jquery-1.3.2.min.js
50 ms
prexClassic.css
40 ms
jsapi
20 ms
google_sitesearch.css
42 ms
urchin.js
21 ms
black-seal-150-110-princetonrecordexchange-16001808.png
180 ms
32 ms
new-header-tl.png
30 ms
new-header-mid.png
31 ms
new-header-tr.png
30 ms
toon-twitter.gif
31 ms
gift-cards.png
29 ms
left-social.gif
30 ms
record-store-day-2015.gif
143 ms
board-end.gif.png
141 ms
customer-reviews.gif
137 ms
news-logos_FN.jpg
140 ms
nj-links.gif.png
142 ms
top-links.gif
148 ms
bot-links.gif
149 ms
mccarter.gif
149 ms
hometown.jpg
149 ms
h-linkBG.gif
149 ms
toon-record.gif.png
148 ms
home.gif.png
169 ms
about.gif.png
168 ms
buy.gif.png
169 ms
sell.gif.png
167 ms
directions.gif.png
168 ms
genres.gif.png
167 ms
trans.gif
180 ms
storePhoto.jpg
191 ms
cheerfullright.gif
178 ms
default+en.css
4 ms
default+en.I.js
11 ms
videoseries
167 ms
__utm.gif
90 ms
printless.css
17 ms
www-embed-player-vflRGs1ko.css
73 ms
www-embed-player.js
96 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
40 ms
ad_status.js
88 ms
prex.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
prex.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
prex.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
US-ASCII
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prex.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 Prex.com main page’s claimed encoding is us-ascii. 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.
prex.com
Open Graph description is not detected on the main page of Prex. 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: