Report Summary

  • 18

    Performance

    Renders faster than
    35% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

box.net

Box — Secure Cloud Content Management, Workflow, and Collaboration

Page Load Speed

80.9 sec in total

First Response

1.7 sec

Resources Loaded

55.7 sec

Page Rendered

23.5 sec

box.net screenshot

About Website

Visit box.net now to see the best up-to-date Box content for United States and also check out these interesting facts you probably never knew about box.net

Box empowers your teams by making it easy to work with people inside and outside your organization, protect your valuable content, and connect all your apps.

Visit box.net

Key Findings

We analyzed Box.net page load time and found that the first response time was 1.7 sec and then it took 79.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

box.net performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value10,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

www.box.com

1700 ms

munchkin.js

663 ms

css_eR-vZ0XMWItVcllcLpaGn5g6faXnDwvVHKchnn72-RY_cBbDv0yYfzzWlzwW8gN5g7ZNNtUSrE7yt39kquJPLPU.css

3900 ms

css

4154 ms

css_5R1ECv7aOL6AmhuhCWKh0_fdllP7QqPTJMxOLTYl65A_cBbDv0yYfzzWlzwW8gN5g7ZNNtUSrE7yt39kquJPLPU.css

4240 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Box.net, 12% (15 requests) were made to Assets.adobedtm.com and 6% (7 requests) were made to Ml314.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Servedby.flashtalking.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (32%)

Content Size

3.7 MB

After Optimization

2.5 MB

In fact, the total size of Box.net main page is 3.7 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 96.5 kB

  • Original 131.7 kB
  • After minification 130.2 kB
  • After compression 35.2 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 96.5 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 1.5 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. Box images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 598.0 kB

  • Original 960.5 kB
  • After minification 922.2 kB
  • After compression 362.5 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 598.0 kB or 62% of the original size.

CSS Optimization

-80%

Potential reduce by 475.1 kB

  • Original 595.8 kB
  • After minification 583.7 kB
  • After compression 120.7 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. Box.net needs all CSS files to be minified and compressed as it can save up to 475.1 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

113

After Optimization

53

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

Accessibility Review

box.net accessibility score

84

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.

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

Image elements do not have [alt] attributes

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

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

box.net SEO score

77

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Box.net 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 Box.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 data is detected on the main page of Box. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: