Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

purchaze.com

Sneaker Online Shop & Sneakerstore - Purchaze

Page Load Speed

6.6 sec in total

First Response

1.4 sec

Resources Loaded

4.5 sec

Page Rendered

775 ms

About Website

Click here to check amazing Purchaze content for Germany. Otherwise, check out these important facts you probably never knew about purchaze.com

Purchaze - Online Sneaker Shop for the latest Nike Air Force 1, Nike Air Max 1, Nike Dunks and Nike Air Jordans.

Visit purchaze.com

Key Findings

We analyzed Purchaze.com page load time and found that the first response time was 1.4 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

purchaze.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.644

9/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

purchaze.com

1389 ms

main.css

332 ms

fancybox.css

244 ms

validationEngine.css

253 ms

chosen.css

252 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 82% of them (106 requests) were addressed to the original Purchaze.com, 5% (6 requests) were made to Apis.google.com and 2% (3 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Purchaze.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 893.9 kB (19%)

Content Size

4.8 MB

After Optimization

3.9 MB

In fact, the total size of Purchaze.com main page is 4.8 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 774.4 kB

  • Original 912.6 kB
  • After minification 896.0 kB
  • After compression 138.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. 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 774.4 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 41.4 kB

  • Original 3.4 MB
  • After minification 3.3 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. Purchaze images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 56.3 kB

  • Original 334.6 kB
  • After minification 334.3 kB
  • After compression 278.3 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 56.3 kB or 17% of the original size.

CSS Optimization

-17%

Potential reduce by 21.7 kB

  • Original 125.3 kB
  • After minification 125.3 kB
  • After compression 103.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. Purchaze.com needs all CSS files to be minified and compressed as it can save up to 21.7 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (53%)

Requests Now

124

After Optimization

58

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

Accessibility Review

purchaze.com accessibility score

84

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

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

Links do not have a discernible name

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

purchaze.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

purchaze.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

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

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