Tools & Wizards About Us
puremarks.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

puremarks.com

Puremarks Technology | eCommerce, Domains, Websites & Emails

Page Load Speed

2.2 sec in total

First Response

476 ms

Resources Loaded

1.5 sec

Page Rendered

231 ms

puremarks.com screenshot

About Website

Welcome to puremarks.com homepage info - get ready to check Puremarks best content for Zambia right away, or after learning these important things about puremarks.com

Puremarks Technology for Domains, Email & Web Hosting, Web Designs, Software Support, E-commerce, Mobile App Development.

Visit puremarks.com

Key Findings

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

Performance Metrics

puremarks.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value990 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.357

30/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

puremarks.com

476 ms

production.css

384 ms

jquery.js

66 ms

cart.js

96 ms

modernizr_webp.js

109 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 14% of them (5 requests) were addressed to the original Puremarks.com, 74% (26 requests) were made to Cdnassets.com and 3% (1 request) were made to Datadoghq-browser-agent.com. The less responsive or slowest element that took the longest time to load (476 ms) belongs to the original domain Puremarks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.7 kB (13%)

Content Size

635.0 kB

After Optimization

550.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Puremarks.com main page is 635.0 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. 35% of websites need less resources to load. Images take 424.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 46.0 kB

  • Original 54.7 kB
  • After minification 35.6 kB
  • After compression 8.7 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 19.2 kB, which is 35% 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 46.0 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 424.5 kB
  • After minification 424.5 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. Puremarks images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 38.7 kB

  • Original 155.7 kB
  • After minification 155.7 kB
  • After compression 117.0 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 38.7 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (47%)

Requests Now

34

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

puremarks.com

puremarks.com

476 ms

production.css

production.css

384 ms

jquery.js

jquery.js

66 ms

cart.js

cart.js

96 ms

modernizr_webp.js

modernizr_webp.js

109 ms

commonScripts.js

commonScripts.js

108 ms

jquery.innerfade.js

jquery.innerfade.js

122 ms

jquery.scrollTo.js

jquery.scrollTo.js

110 ms

homepage.js

homepage.js

119 ms

loading_animation.js

loading_animation.js

122 ms

footerScripts.js

footerScripts.js

127 ms

ga_event_tracking.js

ga_event_tracking.js

132 ms

csrfprotector.js

csrfprotector.js

221 ms

jquery-migrate-3.4.1.min.js

jquery-migrate-3.4.1.min.js

21 ms

jquery.cookie-1.3.1.js

jquery.cookie-1.3.1.js

24 ms

datadog-rum-v3.js

datadog-rum-v3.js

45 ms

logo.gif

logo.gif

41 ms

top-header-icons-sprite.png

top-header-icons-sprite.png

62 ms

menu-sprite.png

menu-sprite.png

38 ms

homepage-banner-2.jpg

homepage-banner-2.jpg

43 ms

bundles-homepage-blurb-dark-sep.png

bundles-homepage-blurb-dark-sep.png

27 ms

dark-bundle-products-sprite.png

dark-bundle-products-sprite.png

42 ms

hp-new-gtld-link.png

hp-new-gtld-link.png

28 ms

promoblurb-arrow.png

promoblurb-arrow.png

42 ms

hp-new-icon.png

hp-new-icon.png

45 ms

gapps-whatsnew-bg.png

gapps-whatsnew-bg.png

44 ms

online-business-icon.png

online-business-icon.png

51 ms

hp-product-icons-sprite.png

hp-product-icons-sprite.png

51 ms

hp-bullet-point.png

hp-bullet-point.png

53 ms

bg-footer.jpg

bg-footer.jpg

34 ms

1fts4h03s

1fts4h03s

207 ms

gtm.js

gtm.js

94 ms

gtmDataLayer.js

gtmDataLayer.js

97 ms

gtm.js

gtm.js

46 ms

analytics.js

analytics.js

16 ms

Accessibility Review

puremarks.com accessibility score

85

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

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

puremarks.com

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