Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

thomasfx.com

Special Effects Supplies and Equipment, Special FX Supplies

Page Load Speed

4.2 sec in total

First Response

112 ms

Resources Loaded

3.6 sec

Page Rendered

536 ms

About Website

Welcome to thomasfx.com homepage info - get ready to check Thomas FX best content for Canada right away, or after learning these important things about thomasfx.com

Thomas FX is a world leader in Professional Special Effects Supplies & Equipment including fake snow, fake ash, movie sand, breakaway glass, pyrotechnics & much more.

Visit thomasfx.com

Key Findings

We analyzed Thomasfx.com page load time and found that the first response time was 112 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

thomasfx.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value114.5 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value10,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.899

3/100

15%

TTI (Time to Interactive)

Value75.3 s

0/100

10%

Network Requests Diagram

www.thomasfx.com

112 ms

bootstrap.min.css

47 ms

style.css

69 ms

jquery-3.3.1.min.js

69 ms

buttons.js

102 ms

Our browser made a total of 198 requests to load all elements on the main page. We found that 79% of them (156 requests) were addressed to the original Thomasfx.com, 5% (9 requests) were made to Static.olark.com and 3% (5 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Thomasfx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 770.7 kB (28%)

Content Size

2.8 MB

After Optimization

2.0 MB

In fact, the total size of Thomasfx.com main page is 2.8 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. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 750.9 kB

  • Original 918.3 kB
  • After minification 917.8 kB
  • After compression 167.4 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 750.9 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 271 B

  • 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. Thomas FX images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 19.6 kB

  • Original 368.7 kB
  • After minification 368.6 kB
  • After compression 349.2 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

-0%

Potential reduce by 19 B

  • Original 114.7 kB
  • After minification 114.7 kB
  • After compression 114.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. Thomasfx.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 91 (49%)

Requests Now

186

After Optimization

95

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

Accessibility Review

thomasfx.com accessibility score

68

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-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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

High

Page has valid source maps

SEO Factors

thomasfx.com SEO score

84

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thomasfx.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 Thomasfx.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 Thomas FX. 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: