Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

jjames.com

Architectural Door Furniture | J.James & Co | Gate Hardware

Page Load Speed

9.9 sec in total

First Response

1.1 sec

Resources Loaded

8 sec

Page Rendered

863 ms

jjames.com screenshot

About Website

Welcome to jjames.com homepage info - get ready to check J James best content right away, or after learning these important things about jjames.com

For the best architectural door furniture in Australia, contact J.James & Co. Experience the pinnacle of style & functionality. Check design options here.

Visit jjames.com

Key Findings

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

Performance Metrics

jjames.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value2,860 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

jjames.com

1061 ms

abgub.css

843 ms

css

34 ms

abguc.js

1024 ms

abguc.js

621 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 67% of them (44 requests) were addressed to the original Jjames.com, 12% (8 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Jjames.com.

Page Optimization Overview & Recommendations

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

Content Size

2.4 MB

After Optimization

2.2 MB

In fact, the total size of Jjames.com main page is 2.4 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 60.3 kB

  • Original 73.8 kB
  • After minification 66.7 kB
  • After compression 13.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 60.3 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 33.2 kB

  • Original 1.7 MB
  • After minification 1.7 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. J James images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 59.7 kB

  • Original 428.0 kB
  • After minification 428.0 kB
  • After compression 368.3 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 59.7 kB or 14% of the original size.

CSS Optimization

-31%

Potential reduce by 75.2 kB

  • Original 244.1 kB
  • After minification 244.1 kB
  • After compression 168.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. Jjames.com needs all CSS files to be minified and compressed as it can save up to 75.2 kB or 31% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

24

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

Accessibility Review

jjames.com 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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

jjames.com 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

jjames.com SEO score

98

Search Engine Optimization Advices

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 Jjames.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 Jjames.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 J James. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: