Tools & Wizards About Us
waxtimes.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

waxtimes.com

Wax Times | Adventures in AnalogWax Times | Adventures in Analog

Page Load Speed

1.3 sec in total

First Response

74 ms

Resources Loaded

836 ms

Page Rendered

380 ms

waxtimes.com screenshot

About Website

Welcome to waxtimes.com homepage info - get ready to check Wax Times best content right away, or after learning these important things about waxtimes.com

Records, analog tech and interviews with people we meet along the way. Founded in Phoenix. Available everywhere.

Visit waxtimes.com

Key Findings

We analyzed Waxtimes.com page load time and found that the first response time was 74 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 25% of websites can load faster.

Performance Metrics

waxtimes.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

72/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.116

85/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

waxtimes.com

74 ms

waxtimes.com

407 ms

css

41 ms

shareaholic.js

31 ms

style.css

22 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 85% of them (64 requests) were addressed to the original Waxtimes.com, 11% (8 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (407 ms) belongs to the original domain Waxtimes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.6 kB (7%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waxtimes.com main page is 1.3 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 65.0 kB

  • Original 79.1 kB
  • After minification 69.4 kB
  • After compression 14.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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 12% 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 65.0 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 27.0 kB

  • Original 1.1 MB
  • After minification 1.1 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. Wax Times images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.9 kB

  • Original 128.1 kB
  • After minification 127.8 kB
  • After compression 126.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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 4.7 kB

  • Original 44.5 kB
  • After minification 44.5 kB
  • After compression 39.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. Waxtimes.com needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (38%)

Requests Now

64

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

waxtimes.com

waxtimes.com

74 ms

waxtimes.com

waxtimes.com

407 ms

css

css

41 ms

shareaholic.js

shareaholic.js

31 ms

style.css

style.css

22 ms

prettyPhoto.css

prettyPhoto.css

39 ms

style-custom.css

style-custom.css

48 ms

social-media.css

social-media.css

49 ms

font-awesome.min.css

font-awesome.min.css

50 ms

mobile.css

mobile.css

48 ms

style.min.css

style.min.css

65 ms

app.css

app.css

58 ms

default.css

default.css

60 ms

jquery.min.js

jquery.min.js

84 ms

jquery-migrate.min.js

jquery-migrate.min.js

62 ms

shortcodes.css

shortcodes.css

62 ms

adsbygoogle.js

adsbygoogle.js

53 ms

tabs.js

tabs.js

72 ms

core.min.js

core.min.js

76 ms

tabs.min.js

tabs.min.js

78 ms

shortcodes.js

shortcodes.js

76 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

79 ms

jquery.flexslider.start.widget.js

jquery.flexslider.start.widget.js

167 ms

superfish.js

superfish.js

166 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

169 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

169 ms

jquery.flexslider.start.main.js

jquery.flexslider.start.main.js

169 ms

ownScript.js

ownScript.js

171 ms

zoom.png

zoom.png

56 ms

waxtimes1.png

waxtimes1.png

56 ms

101215-unboxingVinylMoon.jpg

101215-unboxingVinylMoon.jpg

118 ms

092815-discogsApp.jpg

092815-discogsApp.jpg

112 ms

090815-returningRecords.jpg

090815-returningRecords.jpg

118 ms

082415-trackingRecords.jpg

082415-trackingRecords.jpg

119 ms

081715-originality.jpg

081715-originality.jpg

119 ms

transparent-light.png

transparent-light.png

55 ms

101215-unboxingVinylMoon-95x70.jpg

101215-unboxingVinylMoon-95x70.jpg

111 ms

092815-discogsApp-95x70.jpg

092815-discogsApp-95x70.jpg

118 ms

090815-returningRecords-95x70.jpg

090815-returningRecords-95x70.jpg

137 ms

082415-trackingRecords-95x70.jpg

082415-trackingRecords-95x70.jpg

136 ms

081715-originality-95x70.jpg

081715-originality-95x70.jpg

137 ms

081015-freeRecords-95x70.jpg

081015-freeRecords-95x70.jpg

136 ms

newman-lathe-95x70.jpg

newman-lathe-95x70.jpg

136 ms

042715-discographic-sm1-95x70.jpg

042715-discographic-sm1-95x70.jpg

135 ms

751380441_4f9a1675c3_b-95x70.jpg

751380441_4f9a1675c3_b-95x70.jpg

158 ms

Ledger-95x70.jpg

Ledger-95x70.jpg

160 ms

jazzsurseine-95x70.jpg

jazzsurseine-95x70.jpg

159 ms

11726676724_b4389b7b3e_o-95x70.jpg

11726676724_b4389b7b3e_o-95x70.jpg

160 ms

LostInTranslation-95x70.jpg

LostInTranslation-95x70.jpg

159 ms

vinylhub1-95x70.png

vinylhub1-95x70.png

160 ms

rare-053114-95x70.jpg

rare-053114-95x70.jpg

166 ms

080315-survey2015-95x70.jpg

080315-survey2015-95x70.jpg

168 ms

070615-budgetTables-95x70.jpg

070615-budgetTables-95x70.jpg

167 ms

121514-cleaning-ftr-95x70.jpg

121514-cleaning-ftr-95x70.jpg

167 ms

divider23.png

divider23.png

166 ms

101215-unboxingVinylMoon-300x260.jpg

101215-unboxingVinylMoon-300x260.jpg

167 ms

092815-discogsApp-300x260.jpg

092815-discogsApp-300x260.jpg

186 ms

tDbI2oqRg1oM3QBjjcaDkOr9rADWGQyH.ttf

tDbI2oqRg1oM3QBjjcaDkOr9rADWGQyH.ttf

73 ms

090815-returningRecords-300x260.jpg

090815-returningRecords-300x260.jpg

140 ms

082415-trackingRecords-300x260.jpg

082415-trackingRecords-300x260.jpg

138 ms

081715-originality-300x260.jpg

081715-originality-300x260.jpg

140 ms

081015-freeRecords-300x260.jpg

081015-freeRecords-300x260.jpg

138 ms

search-submit.png

search-submit.png

134 ms

up.png

up.png

148 ms

raxhHiqOu8IVPmnRc6SY1KXhnF_Y8fbfOLjOWHpzveSJBA.ttf

raxhHiqOu8IVPmnRc6SY1KXhnF_Y8fbfOLjOWHpzveSJBA.ttf

8 ms

raxhHiqOu8IVPmnRc6SY1KXhnF_Y8RHYOLjOWHpzveSJBA.ttf

raxhHiqOu8IVPmnRc6SY1KXhnF_Y8RHYOLjOWHpzveSJBA.ttf

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

29 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

31 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

31 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf

30 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

87 ms

transparent-dark.png

transparent-dark.png

17 ms

nav_left_t.png

nav_left_t.png

17 ms

nav_right_t.png

nav_right_t.png

17 ms

Accessibility Review

waxtimes.com accessibility score

82

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

Form elements do not have associated labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

waxtimes.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

waxtimes.com SEO score

86

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

waxtimes.com

Open Graph data is detected on the main page of Wax Times. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: