Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

borders.com

Barnes & Noble Welcomes Borders® Bookstore Customers | Barnes & Noble®

Page Load Speed

154.8 sec in total

First Response

1.5 sec

Resources Loaded

143.2 sec

Page Rendered

10.1 sec

borders.com screenshot

About Website

Visit borders.com now to see the best up-to-date Borders content and also check out these interesting facts you probably never knew about borders.com

Barnes & Noble® welcomes Borders®, Waldenbooks® and their customers to discover their next great read at Barnes & Noble.

Visit borders.com

Key Findings

We analyzed Borders.com page load time and found that the first response time was 1.5 sec and then it took 153.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

borders.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value9,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value26.4 s

0/100

10%

Network Requests Diagram

borders

1503 ms

css

1533 ms

toolkit.min.css

3690 ms

toolkit-header-new.min.css

3099 ms

vendor.js

5698 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Borders.com, 13% (15 requests) were made to Prodimage.images-bn.com and 10% (12 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (33.5 sec) relates to the external source Tpc.googlesyndication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.4 MB (57%)

Content Size

5.9 MB

After Optimization

2.5 MB

In fact, the total size of Borders.com main page is 5.9 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. 80% 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. Javascripts take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 255.8 kB

  • Original 298.4 kB
  • After minification 290.6 kB
  • After compression 42.5 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 255.8 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 54.8 kB

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

JavaScript Optimization

-71%

Potential reduce by 2.4 MB

  • Original 3.3 MB
  • After minification 3.1 MB
  • After compression 956.9 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 2.4 MB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 686.9 kB

  • Original 818.9 kB
  • After minification 808.2 kB
  • After compression 131.9 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. Borders.com needs all CSS files to be minified and compressed as it can save up to 686.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (72%)

Requests Now

93

After Optimization

26

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

Accessibility Review

borders.com accessibility score

60

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

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

borders.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

borders.com SEO score

70

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