Tools & Wizards About Us
instabox.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

instabox.com

Instabox ♥ Uncomplicated shipping

Page Load Speed

657 ms in total

First Response

52 ms

Resources Loaded

550 ms

Page Rendered

55 ms

instabox.com screenshot

About Website

Click here to check amazing Instabox content for Canada. Otherwise, check out these important facts you probably never knew about instabox.com

Visit instabox.com

Key Findings

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

instabox.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value600 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

instabox.com

52 ms

instabox.io

267 ms

en-SE

134 ms

446dc775d2a0a12d.css

26 ms

01c7fca41aca0ead.css

24 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Instabox.com, 94% (17 requests) were made to Instabox.io. The less responsive or slowest element that took the longest time to load (267 ms) relates to the external source Instabox.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.4 kB (11%)

Content Size

2.4 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Instabox.com main page is 2.4 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. 70% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 21.7 kB

  • Original 31.4 kB
  • After minification 31.4 kB
  • After compression 9.8 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 21.7 kB or 69% of the original size.

Image Optimization

-1%

Potential reduce by 17.9 kB

  • Original 2.0 MB
  • After minification 2.0 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. Instabox images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 131.5 kB

  • Original 240.5 kB
  • After minification 240.3 kB
  • After compression 109.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 131.5 kB or 55% of the original size.

CSS Optimization

-83%

Potential reduce by 90.4 kB

  • Original 108.7 kB
  • After minification 107.9 kB
  • After compression 18.3 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. Instabox.com needs all CSS files to be minified and compressed as it can save up to 90.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (73%)

Requests Now

11

After Optimization

3

  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Instabox. 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 as a result speed up the page load time.

Network Requests Diagram

instabox.com

instabox.com

52 ms

instabox.io

instabox.io

267 ms

en-SE

en-SE

134 ms

446dc775d2a0a12d.css

446dc775d2a0a12d.css

26 ms

01c7fca41aca0ead.css

01c7fca41aca0ead.css

24 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

34 ms

webpack-0df3c27e9d3803e7.js

webpack-0df3c27e9d3803e7.js

29 ms

framework-0f3330e6efb75f4c.js

framework-0f3330e6efb75f4c.js

30 ms

main-8c96dfafccc9fb4f.js

main-8c96dfafccc9fb4f.js

31 ms

_app-65dbeadaf84f6352.js

_app-65dbeadaf84f6352.js

59 ms

464-dbf3d88f094e267e.js

464-dbf3d88f094e267e.js

55 ms

index-6b0f8950a6c512d2.js

index-6b0f8950a6c512d2.js

56 ms

_buildManifest.js

_buildManifest.js

56 ms

_ssgManifest.js

_ssgManifest.js

57 ms

CircularXXWeb-Regular.dd2df163.woff

CircularXXWeb-Regular.dd2df163.woff

18 ms

CircularXXWeb-Book.e21dcd4b.woff

CircularXXWeb-Book.e21dcd4b.woff

17 ms

CircularXXWeb-Medium.dabb9ae9.woff

CircularXXWeb-Medium.dabb9ae9.woff

14 ms

CircularXXWeb-Bold.92dda119.woff

CircularXXWeb-Bold.92dda119.woff

30 ms

Accessibility Review

instabox.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

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

Page has valid source maps

SEO Factors

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

Links do not have descriptive text

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

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

instabox.com

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