Tools & Wizards About Us
pure42.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

pure42.com

Hybrid Web Developer / Programmer, Technical Consultant and Design Technologist, with a creative twist | JasonMayes.com

Page Load Speed

2.2 sec in total

First Response

98 ms

Resources Loaded

1.4 sec

Page Rendered

769 ms

pure42.com screenshot

About Website

Visit pure42.com now to see the best up-to-date Pure 42 content and also check out these interesting facts you probably never knew about pure42.com

Jason Mayes - Hybrid Web Developer / Programmer, Technical Consultant, and Design Technologist, with a creative twist based in London, UK. Hire Me. Skillsets: HTML5, CSS, CSS3, JavaScript, JQuery, Nod...

Visit pure42.com

Key Findings

We analyzed Pure42.com page load time and found that the first response time was 98 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pure42.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value19,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value30.9 s

0/100

10%

Network Requests Diagram

pure42.com

98 ms

css

26 ms

style.css

31 ms

zQ2wup7ACa0

148 ms

8EA_dLheKpc

142 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 36% of them (14 requests) were addressed to the original Pure42.com, 46% (18 requests) were made to Youtube.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (881 ms) relates to the external source Static.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.7 kB (23%)

Content Size

1.0 MB

After Optimization

806.4 kB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Pure42.com main page is 1.0 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. Only a small number of websites need less resources to load. Javascripts take 520.5 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-3%

Potential reduce by 12.6 kB

  • Original 398.3 kB
  • After minification 385.7 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. Pure 42 images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 221.5 kB

  • Original 520.5 kB
  • After minification 520.5 kB
  • After compression 298.9 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 221.5 kB or 43% of the original size.

CSS Optimization

-0%

Potential reduce by 550 B

  • Original 122.3 kB
  • After minification 122.3 kB
  • After compression 121.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. Pure42.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (30%)

Requests Now

37

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pure42.com

pure42.com

98 ms

css

css

26 ms

style.css

style.css

31 ms

zQ2wup7ACa0

zQ2wup7ACa0

148 ms

8EA_dLheKpc

8EA_dLheKpc

142 ms

PJm8WNajZtw

PJm8WNajZtw

135 ms

3FrYr13RL1E

3FrYr13RL1E

139 ms

2TAimu6w2rg

2TAimu6w2rg

136 ms

x1JYnsvvaJs

x1JYnsvvaJs

143 ms

kFtIddNLcuM

kFtIddNLcuM

615 ms

EuO7XDLHaIc

EuO7XDLHaIc

658 ms

pTYludnVIpA

pTYludnVIpA

875 ms

MCqDoX6j_eA

MCqDoX6j_eA

875 ms

1RGtj8WKZ_c

1RGtj8WKZ_c

874 ms

jmEngine-min.js

jmEngine-min.js

53 ms

titlebar_logo.png

titlebar_logo.png

60 ms

leftBannerBack.png

leftBannerBack.png

63 ms

rightBannerBack.png

rightBannerBack.png

63 ms

jmtact.png

jmtact.png

63 ms

back_texture.jpg

back_texture.jpg

38 ms

titlebar_back.png

titlebar_back.png

102 ms

social_icons.png

social_icons.png

105 ms

teaser2.jpg

teaser2.jpg

848 ms

recommendations.jpg

recommendations.jpg

112 ms

footer_back.jpg

footer_back.jpg

104 ms

mayes_crest.png

mayes_crest.png

184 ms

ga.js

ga.js

10 ms

__utm.gif

__utm.gif

44 ms

www-player.css

www-player.css

14 ms

www-embed-player.js

www-embed-player.js

41 ms

base.js

base.js

83 ms

www-player.css

www-player.css

330 ms

www-embed-player.js

www-embed-player.js

438 ms

base.js

base.js

739 ms

font

font

69 ms

collect

collect

704 ms

ad_status.js

ad_status.js

881 ms

2yHxwLnpFNEqACbXxmWZxf-EiWnnfWrHZJA47psUYZk.js

2yHxwLnpFNEqACbXxmWZxf-EiWnnfWrHZJA47psUYZk.js

673 ms

embed.js

embed.js

303 ms

Accessibility Review

pure42.com accessibility score

53

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

pure42.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

pure42.com SEO score

92

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

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pure42.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 Pure42.com main page’s claimed encoding is . 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.

Social Sharing Optimization

pure42.com

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