Tools & Wizards About Us
primarywave.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

primarywave.com

Primary Wave Music - The Home of Legends

Page Load Speed

5.2 sec in total

First Response

2.1 sec

Resources Loaded

2.9 sec

Page Rendered

170 ms

primarywave.com screenshot

About Website

Welcome to primarywave.com homepage info - get ready to check Primary Wave best content for United States right away, or after learning these important things about primarywave.com

Official website for the leading independent publisher of iconic music in the world. The songs represented include over 1,000 Top 10 singles, and over 400 #1 hits.

Visit primarywave.com

Key Findings

We analyzed Primarywave.com page load time and found that the first response time was 2.1 sec 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.

Performance Metrics

primarywave.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.566

12/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

www.primarywave.com

2083 ms

all.0.0.2.css

44 ms

jquery.js

9 ms

jquery-ui.js

18 ms

swfobject.js

18 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Primarywave.com, 40% (16 requests) were made to Synchtank-cdn.s3.amazonaws.com and 25% (10 requests) were made to D2n4yiee7lv24r.cloudfront.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Primarywave.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (36%)

Content Size

3.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Primarywave.com main page is 3.1 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. 75% 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. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 27.7 kB

  • Original 35.9 kB
  • After minification 30.6 kB
  • After compression 8.2 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 5.3 kB, which is 15% 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 27.7 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 80.1 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. Primary Wave images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 812.1 kB

  • Original 1.0 MB
  • After minification 786.5 kB
  • After compression 229.4 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 812.1 kB or 78% of the original size.

CSS Optimization

-87%

Potential reduce by 205.7 kB

  • Original 237.3 kB
  • After minification 186.2 kB
  • After compression 31.5 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. Primarywave.com needs all CSS files to be minified and compressed as it can save up to 205.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

35

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Primary Wave. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.primarywave.com

www.primarywave.com

2083 ms

all.0.0.2.css

all.0.0.2.css

44 ms

jquery.js

jquery.js

9 ms

jquery-ui.js

jquery-ui.js

18 ms

swfobject.js

swfobject.js

18 ms

select2.min.js

select2.min.js

10 ms

all.1.1.4.8.gz.js

all.1.1.4.8.gz.js

91 ms

ga.js

ga.js

163 ms

9354616.jpg

9354616.jpg

121 ms

music-player-logo.png

music-player-logo.png

46 ms

header-logo.png

header-logo.png

62 ms

social-sprite.png

social-sprite.png

62 ms

background.gif

background.gif

51 ms

separator.gif

separator.gif

59 ms

loading-bar.gif

loading-bar.gif

60 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

69 ms

loading.gif

loading.gif

83 ms

arrows.png

arrows.png

210 ms

www.primarywave.com

www.primarywave.com

581 ms

2726026.jpg

2726026.jpg

28 ms

2738756.jpg

2738756.jpg

86 ms

2726018.jpg

2726018.jpg

183 ms

2738758.jpg

2738758.jpg

42 ms

2738760.jpg

2738760.jpg

66 ms

2726022.jpg

2726022.jpg

77 ms

2726024.jpg

2726024.jpg

57 ms

17867828.jpg

17867828.jpg

120 ms

17898046.jpg

17898046.jpg

68 ms

17789662.jpg

17789662.jpg

120 ms

15799354.jpg

15799354.jpg

98 ms

15660800.jpg

15660800.jpg

119 ms

13483902.jpg

13483902.jpg

110 ms

13476360.jpg

13476360.jpg

111 ms

13475764.jpg

13475764.jpg

158 ms

HelveticaRegular.woff

HelveticaRegular.woff

144 ms

HelveticaBold.woff

HelveticaBold.woff

63 ms

HelveticaLight.woff

HelveticaLight.woff

47 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

80 ms

__utm.gif

__utm.gif

13 ms

__utm.gif

__utm.gif

19 ms

Accessibility Review

primarywave.com accessibility score

92

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

primarywave.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

primarywave.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Primarywave.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 Primarywave.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.

Social Sharing Optimization

primarywave.com

Open Graph description is not detected on the main page of Primary Wave. 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: