Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

builder.thompson.com

Employee Handbook Builder: Build, update and customize employee handbooks

Page Load Speed

756 ms in total

First Response

36 ms

Resources Loaded

563 ms

Page Rendered

157 ms

builder.thompson.com screenshot

About Website

Click here to check amazing Builder Thompson content for United States. Otherwise, check out these important facts you probably never knew about builder.thompson.com

The Employee Handbook Builder from BLR – learn how this tool allows you to create and update compliant employee handbooks.

Visit builder.thompson.com

Key Findings

We analyzed Builder.thompson.com page load time and found that the first response time was 36 ms and then it took 720 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

builder.thompson.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value400 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

builder.thompson.com

36 ms

handbookbuilder.blr.com

305 ms

gtm.js

55 ms

js

169 ms

GA_Remarketing_Tag.js

7 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Builder.thompson.com, 89% (39 requests) were made to Handbookbuilder.blr.com and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (305 ms) relates to the external source Handbookbuilder.blr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 298.1 kB (57%)

Content Size

518.7 kB

After Optimization

220.7 kB

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

HTML Optimization

-76%

Potential reduce by 22.1 kB

  • Original 29.0 kB
  • After minification 20.5 kB
  • After compression 6.9 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 8.4 kB, which is 29% 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 22.1 kB or 76% of the original size.

Image Optimization

-65%

Potential reduce by 230.5 kB

  • Original 354.5 kB
  • After minification 123.9 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, Builder Thompson needs image optimization as it can save up to 230.5 kB or 65% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-30%

Potential reduce by 32.3 kB

  • Original 109.3 kB
  • After minification 109.1 kB
  • After compression 76.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 32.3 kB or 30% of the original size.

CSS Optimization

-50%

Potential reduce by 13.1 kB

  • Original 26.0 kB
  • After minification 26.0 kB
  • After compression 12.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. Builder.thompson.com needs all CSS files to be minified and compressed as it can save up to 13.1 kB or 50% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (31%)

Requests Now

35

After Optimization

24

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

Accessibility Review

builder.thompson.com accessibility score

45

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

builder.thompson.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

builder.thompson.com SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Builder.thompson.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 Builder.thompson.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 description is not detected on the main page of Builder Thompson. 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: