Tools & Wizards About Us
puretabs.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

puretabs.com

Page Load Speed

1.3 sec in total

First Response

62 ms

Resources Loaded

1 sec

Page Rendered

233 ms

puretabs.com screenshot

About Website

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

Forsale Lander

Visit puretabs.com

Key Findings

We analyzed Puretabs.com page load time and found that the first response time was 62 ms and then it took 1.3 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

puretabs.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

51/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

puretabs.com

62 ms

puretabs.com

343 ms

uxcore2.min.css

87 ms

noheader.min.css

83 ms

bff84d4aa62dc034.css

65 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Puretabs.com, 53% (18 requests) were made to Godaddy.com and 24% (8 requests) were made to Img6.wsimg.com. The less responsive or slowest element that took the longest time to load (714 ms) relates to the external source Godaddy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.4 kB (38%)

Content Size

180.1 kB

After Optimization

111.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Puretabs.com main page is 180.1 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. 45% of websites need less resources to load. HTML takes 95.8 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 64.5 kB

  • Original 95.8 kB
  • After minification 95.8 kB
  • After compression 31.4 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 64.5 kB or 67% of the original size.

JavaScript Optimization

-0%

Potential reduce by 188 B

  • Original 47.0 kB
  • After minification 47.0 kB
  • After compression 46.8 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

-10%

Potential reduce by 3.8 kB

  • Original 37.3 kB
  • After minification 37.1 kB
  • After compression 33.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. Puretabs.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (87%)

Requests Now

30

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

puretabs.com

puretabs.com

62 ms

puretabs.com

puretabs.com

343 ms

uxcore2.min.css

uxcore2.min.css

87 ms

noheader.min.css

noheader.min.css

83 ms

bff84d4aa62dc034.css

bff84d4aa62dc034.css

65 ms

cf230d06d2a86184.css

cf230d06d2a86184.css

129 ms

bfe2d755e7d21e76.css

bfe2d755e7d21e76.css

102 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

100 ms

webpack-abd428484949c941.js

webpack-abd428484949c941.js

99 ms

main-999f8182f179b553.js

main-999f8182f179b553.js

144 ms

framework-f7ba292b22b03fed.js

framework-f7ba292b22b03fed.js

123 ms

_app-6a51282f8efae752.js

_app-6a51282f8efae752.js

114 ms

978-52af53123a2cdee7.js

978-52af53123a2cdee7.js

208 ms

932-5f8574b507db60dc.js

932-5f8574b507db60dc.js

714 ms

%5Bdomain%5D-2fb839cf79e515a4.js

%5Bdomain%5D-2fb839cf79e515a4.js

149 ms

_buildManifest.js

_buildManifest.js

149 ms

_ssgManifest.js

_ssgManifest.js

143 ms

_middlewareManifest.js

_middlewareManifest.js

203 ms

polyfill.min.js

polyfill.min.js

101 ms

uxcore2.min.js

uxcore2.min.js

91 ms

vendor~uxcore2.min.js

vendor~uxcore2.min.js

92 ms

heartbeat.js

heartbeat.js

90 ms

noheader.min.js

noheader.min.js

92 ms

AUs

AUs

57 ms

utag.js

utag.js

89 ms

AUs

AUs

167 ms

gtm.js

gtm.js

67 ms

utag.7.js

utag.7.js

33 ms

analytics.js

analytics.js

39 ms

utag.v.js

utag.v.js

11 ms

tcc.min.js

tcc.min.js

33 ms

collect

collect

37 ms

collect

collect

32 ms

AUs

AUs

105 ms

Accessibility Review

puretabs.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

puretabs.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

Missing source maps for large first-party JavaScript

SEO Factors

puretabs.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puretabs.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Puretabs.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

puretabs.com

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