4.2 sec in total
179 ms
3.3 sec
732 ms
Click here to check amazing PAPERCASTLE RECORDS content. Otherwise, check out these important facts you probably never knew about papercastlerecords.com
Visit papercastlerecords.comWe analyzed Papercastlerecords.com page load time and found that the first response time was 179 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
papercastlerecords.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value26.1 s
0/100
25%
Value19.5 s
0/100
10%
Value19,760 ms
0/100
30%
Value0.067
97/100
15%
Value49.1 s
0/100
10%
179 ms
137 ms
186 ms
205 ms
453 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 18% of them (8 requests) were addressed to the original Papercastlerecords.com, 23% (10 requests) were made to Youtube.com and 11% (5 requests) were made to Assets.squarespace.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Images.squarespace-cdn.com.
Page size can be reduced by 623.0 kB (70%)
890.0 kB
267.0 kB
In fact, the total size of Papercastlerecords.com main page is 890.0 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 337.6 kB which makes up the majority of the site volume.
Potential reduce by 236.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 236.1 kB or 87% of the original size.
Potential reduce by 0 B
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. PAPERCASTLE RECORDS images are well optimized though.
Potential reduce by 100.1 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 100.1 kB or 61% of the original size.
Potential reduce by 286.8 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. Papercastlerecords.com needs all CSS files to be minified and compressed as it can save up to 286.8 kB or 85% of the original size.
Number of requests can be reduced by 16 (43%)
37
21
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PAPERCASTLE RECORDS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.papercastlerecords.com
179 ms
G1-nZaeeUJON8tDFX9nfALYoYmSQThZKebM1YTkQiftfezGgfFHN4UJLFRbh52jhWDm8w2sq5A9owQ6U5A9hwD6DFRwUFQycwg77MPG0SeB3ZW4RjWFXdemkZAFzScsDO1FUiABkZWF3jAF8OcFzdPUCdhFydeyzSabCSeB3ZW4RjWFXdemkZAFzScsDOcFzdPU3jWg8ScFySasCZW48jhNkZYw0SaBujW48Sagyjh90jhNlOYiaiko3jWg8ScFySasCZW48jhNkZYw0jhNlOYiaiko3jWg8ScFySasCZW48jhNkZYw0SaBujW48Sagyjh90jhNlJ68ciWsuScIlSYb7fbRxmgMMeM96MKG4f54oIMMjgKMfqMeVX-Q3gb.js
137 ms
css
186 ms
common-vendors-c563fb79948999a89a36d-min.en-US.js
205 ms
common-96f024e5ffdd31a2223e6-min.en-US.js
453 ms
performance-ea2ccd862828388f851b5-min.en-US.js
454 ms
site.css
238 ms
site-bundle.js
165 ms
site-common.js
149 ms
plugin-lightbox.css
55 ms
plugin-lightbox.js
16 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
754 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
756 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
757 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
756 ms
d
6 ms
d
26 ms
diffuser.js
761 ms
settings
496 ms
Header.png
1772 ms
Nf5o2HzO8Qo
730 ms
XTAdeHQLWss
870 ms
WxzZq3hXojk
938 ms
ArEk-dc8u7I
932 ms
LrvrJRd_Azo
928 ms
lHgggLDtH9g
921 ms
announcement-bar-bb9f86723699f87fdaf2f-min.en-US.js
66 ms
legacy-async-intersection-observer-c1f72be75ae7957a54557-min.en-US.js
60 ms
RecordHit
451 ms
button-render
469 ms
button-render
540 ms
Arrows.png
482 ms
2.png
588 ms
3.png
1518 ms
Awaken+2.0+-+cover.jpg
730 ms
p.gif
476 ms
prism.app-us1.com
209 ms
developer-hidden-pcr-newsletter-1
84 ms
developer-hidden-pcr-newsletter-1
110 ms
www-player.css
80 ms
www-embed-player.js
160 ms
base.js
260 ms
fetch-polyfill.js
200 ms
developer-hidden-pcr-newsletter-1
149 ms
papercastlerecords.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
papercastlerecords.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
papercastlerecords.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 Papercastlerecords.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 Papercastlerecords.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.
papercastlerecords.com
Open Graph description is not detected on the main page of PAPERCASTLE RECORDS. 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: