Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

inkstone.net

Wine, Pet, Fishing, Ski, Golf, Amusement Parks, Skyscraper, Sushi, Shoes themed Playing Card and Gifts from Inkstone, Inc - Missoula, Montana

Page Load Speed

831 ms in total

First Response

185 ms

Resources Loaded

559 ms

Page Rendered

87 ms

About Website

Visit inkstone.net now to see the best up-to-date Inkstone content and also check out these interesting facts you probably never knew about inkstone.net

Specializing in novelty card games and products for the entertainment of friends and family of all ages. Smile!

Visit inkstone.net

Key Findings

We analyzed Inkstone.net page load time and found that the first response time was 185 ms and then it took 646 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

inkstone.net performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.6 s

100/100

10%

Network Requests Diagram

inkstone.net

185 ms

TextStyles.css

69 ms

Layout.css

122 ms

TextFormatting.css

126 ms

Logo.png

124 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Inkstone.net, 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (373 ms) belongs to the original domain Inkstone.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 443.3 kB (83%)

Content Size

536.1 kB

After Optimization

92.7 kB

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

HTML Optimization

-78%

Potential reduce by 8.0 kB

  • Original 10.3 kB
  • After minification 9.4 kB
  • After compression 2.3 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 8.0 kB or 78% of the original size.

Image Optimization

-86%

Potential reduce by 434.8 kB

  • Original 507.0 kB
  • After minification 72.1 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. Obviously, Inkstone needs image optimization as it can save up to 434.8 kB or 86% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-29%

Potential reduce by 467 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 1.1 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. Inkstone.net needs all CSS files to be minified and compressed as it can save up to 467 B or 29% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inkstone. According to our analytics all requests are already optimized.

Accessibility Review

inkstone.net 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

Best Practices

inkstone.net best practices score

75

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

SEO Factors

inkstone.net SEO score

75

Search Engine Optimization Advices

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 Inkstone.net 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 Inkstone.net 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 Inkstone. 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: