2.2 sec in total
330 ms
1.6 sec
260 ms
Click here to check amazing What Are Records content for United States. Otherwise, check out these important facts you probably never knew about whatarerecords.com
Visit whatarerecords.comWe analyzed Whatarerecords.com page load time and found that the first response time was 330 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
whatarerecords.com performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value5.9 s
14/100
25%
Value0.9 s
100/100
10%
Value0 ms
100/100
30%
Value0.131
81/100
15%
Value0.9 s
100/100
10%
330 ms
239 ms
333 ms
389 ms
250 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that all of those requests were addressed to Whatarerecords.com and no external sources were called. The less responsive or slowest element that took the longest time to load (890 ms) belongs to the original domain Whatarerecords.com.
Page size can be reduced by 69.7 kB (9%)
807.5 kB
737.7 kB
In fact, the total size of Whatarerecords.com main page is 807.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 763.9 kB which makes up the majority of the site volume.
Potential reduce by 36.6 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 13.6 kB, which is 31% 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.6 kB or 84% of the original size.
Potential reduce by 33.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. What Are Records images are well optimized though.
Number of requests can be reduced by 7 (37%)
19
12
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Are Records. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
www.whatarerecords.com
330 ms
DavidWilcox-WARSite.jpg
239 ms
home_page_banner.gif
333 ms
OH_home_page_banner.gif
389 ms
store.gif
250 ms
artists.gif
309 ms
news.gif
334 ms
about_us.gif
360 ms
Blaze-cover-small.jpg
469 ms
TTT-120px.png
484 ms
NMfaNW-120px.png
540 ms
shinepotions.jpg
522 ms
Lioncover(600x600).jpg
890 ms
BurrEU120.jpg
683 ms
CD120.jpg
702 ms
EK-cover-120px.jpg
837 ms
store_over.gif
93 ms
artists_over.gif
93 ms
news_over.gif
94 ms
about_us_over.gif
119 ms
whatarerecords.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.
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
<object> elements do not have alternate text
whatarerecords.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
whatarerecords.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
Document uses plugins
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatarerecords.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 Whatarerecords.com main page’s claimed encoding is iso-8859-1. 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.
whatarerecords.com
Open Graph description is not detected on the main page of What Are 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: