Tools & Wizards About Us
physicalassets.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% 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

  • 85

    SEO

    Google-friendlier than
    55% of websites

physicalassets.com

Exercise Equipment Toronto, Physical Assets, Ellipticals, Bikes, Treadmills, Home Gyms,

Page Load Speed

2 sec in total

First Response

252 ms

Resources Loaded

1.4 sec

Page Rendered

263 ms

physicalassets.com screenshot

About Website

Welcome to physicalassets.com homepage info - get ready to check Physical Assets best content right away, or after learning these important things about physicalassets.com

Toronto's supplier of exercise bikes, treadmills, ellipticals, weight equipment, Power Plate, Cross Trainers and professional sales and service since 1984.

Visit physicalassets.com

Key Findings

We analyzed Physicalassets.com page load time and found that the first response time was 252 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

physicalassets.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value4.1 s

80/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

physicalassets.com

252 ms

www.physicalassets.com

188 ms

www.physicalassets.com

299 ms

jquery-ui.css

41 ms

bootstrap.min.css

74 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 41% of them (18 requests) were addressed to the original Physicalassets.com, 32% (14 requests) were made to Fonts.gstatic.com and 9% (4 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (445 ms) belongs to the original domain Physicalassets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 48.7 kB (9%)

Content Size

525.5 kB

After Optimization

476.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 22.7 kB

  • Original 30.7 kB
  • After minification 27.1 kB
  • After compression 8.0 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 3.6 kB, which is 12% 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.7 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 6.3 kB

  • Original 372.7 kB
  • After minification 366.4 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. Physical Assets images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 2.7 kB

  • Original 101.1 kB
  • After minification 99.2 kB
  • After compression 98.4 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

-81%

Potential reduce by 17.0 kB

  • Original 21.0 kB
  • After minification 13.2 kB
  • After compression 4.0 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. Physicalassets.com needs all CSS files to be minified and compressed as it can save up to 17.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (46%)

Requests Now

26

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

physicalassets.com

physicalassets.com

252 ms

www.physicalassets.com

www.physicalassets.com

188 ms

www.physicalassets.com

www.physicalassets.com

299 ms

jquery-ui.css

jquery-ui.css

41 ms

bootstrap.min.css

bootstrap.min.css

74 ms

all.min.css

all.min.css

47 ms

site.css

site.css

64 ms

css2

css2

80 ms

animate.min.css

animate.min.css

58 ms

css2

css2

94 ms

jquery.min.js

jquery.min.js

45 ms

jquery-ui.min.js

jquery-ui.min.js

53 ms

bootstrap.min.js

bootstrap.min.js

84 ms

swfobject.js

swfobject.js

50 ms

json.js

json.js

130 ms

scroll-out.min.js

scroll-out.min.js

67 ms

defaults.css

defaults.css

130 ms

scroll-out.min.js

scroll-out.min.js

16 ms

53308d8f-a497-4388-980e-a96f35805ac6

53308d8f-a497-4388-980e-a96f35805ac6

76 ms

d16e844a-4bf7-41b1-850f-78e7dc744a40

d16e844a-4bf7-41b1-850f-78e7dc744a40

322 ms

8f7f6cba-0449-4957-b35e-d5cd60c98c80

8f7f6cba-0449-4957-b35e-d5cd60c98c80

141 ms

242cb3e3-ef9a-439c-a378-2e1984aee476

242cb3e3-ef9a-439c-a378-2e1984aee476

206 ms

68f1f4f3-a889-4a99-b3d3-d71339992078

68f1f4f3-a889-4a99-b3d3-d71339992078

254 ms

8751f689-78e9-45b4-b32d-3f910488f202

8751f689-78e9-45b4-b32d-3f910488f202

257 ms

0f8e12fd-bcf1-47d0-bd5f-dc0fc40e1111

0f8e12fd-bcf1-47d0-bd5f-dc0fc40e1111

262 ms

242d58cf-5ead-475c-bce7-2fca5910c5ca

242d58cf-5ead-475c-bce7-2fca5910c5ca

257 ms

6b63f303-6708-4433-b2fe-4e239d6d7db6

6b63f303-6708-4433-b2fe-4e239d6d7db6

270 ms

6345c387-84a9-4388-bb9e-99dea1914540

6345c387-84a9-4388-bb9e-99dea1914540

317 ms

de003387-ce70-449b-9350-171430443f8a

de003387-ce70-449b-9350-171430443f8a

323 ms

502b2186-c064-40de-821e-77b4f281a3db

502b2186-c064-40de-821e-77b4f281a3db

445 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

29 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

41 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

40 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

40 ms

pxiByp8kv8JHgFVrLDD4V1s.ttf

pxiByp8kv8JHgFVrLDD4V1s.ttf

38 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

51 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

52 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

51 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

52 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

50 ms

pxiGyp8kv8JHgFVrLPTedw.ttf

pxiGyp8kv8JHgFVrLPTedw.ttf

51 ms

Accessibility Review

physicalassets.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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

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

SEO Factors

physicalassets.com SEO score

85

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

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

physicalassets.com

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