Tools & Wizards About Us
dirtyjanes.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

dirtyjanes.com

Dirty Janes Antique Market | Bowral | Offering the best of Vintage

Page Load Speed

12.9 sec in total

First Response

3.2 sec

Resources Loaded

9.4 sec

Page Rendered

317 ms

dirtyjanes.com screenshot

About Website

Welcome to dirtyjanes.com homepage info - get ready to check Dirty Janes best content right away, or after learning these important things about dirtyjanes.com

Dirty Janes antique market is located in Bowral, offering the best in vintage. Over 50 dealers offer wonderful pieces from furnishings ornaments & jewellery

Visit dirtyjanes.com

Key Findings

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

Performance Metrics

dirtyjanes.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value21.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,360 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

dirtyjanes.com

3244 ms

sbi-styles.min.css

644 ms

style.min.css

868 ms

styles.css

648 ms

woocommerce-layout.css

651 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 89% of them (81 requests) were addressed to the original Dirtyjanes.com, 5% (5 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Dirtyjanes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (46%)

Content Size

3.7 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dirtyjanes.com main page is 3.7 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. 75% 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 1.1 MB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 92.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. 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 1.1 MB or 92% of the original size.

Image Optimization

-31%

Potential reduce by 620.4 kB

  • Original 2.0 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. Obviously, Dirty Janes needs image optimization as it can save up to 620.4 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 423 B

  • Original 332.1 kB
  • After minification 332.1 kB
  • After compression 331.7 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

-3%

Potential reduce by 5.4 kB

  • Original 192.3 kB
  • After minification 192.3 kB
  • After compression 186.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. Dirtyjanes.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 78 (94%)

Requests Now

83

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dirtyjanes.com

dirtyjanes.com

3244 ms

sbi-styles.min.css

sbi-styles.min.css

644 ms

style.min.css

style.min.css

868 ms

styles.css

styles.css

648 ms

woocommerce-layout.css

woocommerce-layout.css

651 ms

woocommerce.css

woocommerce.css

648 ms

style.css

style.css

653 ms

front.css

front.css

856 ms

um-modal.min.css

um-modal.min.css

863 ms

jquery-ui.min.css

jquery-ui.min.css

866 ms

tipsy.min.css

tipsy.min.css

866 ms

um-raty.min.css

um-raty.min.css

870 ms

select2.min.css

select2.min.css

1072 ms

um-fileupload.min.css

um-fileupload.min.css

1077 ms

um-confirm.min.css

um-confirm.min.css

1080 ms

default.min.css

default.min.css

1081 ms

default.date.min.css

default.date.min.css

1080 ms

default.time.min.css

default.time.min.css

1082 ms

fonticons-ii.min.css

fonticons-ii.min.css

1288 ms

fonticons-fa.min.css

fonticons-fa.min.css

1293 ms

um-fontawesome.min.css

um-fontawesome.min.css

1521 ms

common.min.css

common.min.css

1295 ms

um-responsive.min.css

um-responsive.min.css

1310 ms

um-styles.min.css

um-styles.min.css

1299 ms

cropper.min.css

cropper.min.css

1503 ms

um-profile.min.css

um-profile.min.css

1508 ms

um-account.min.css

um-account.min.css

1511 ms

um-misc.min.css

um-misc.min.css

1515 ms

um-old-default.min.css

um-old-default.min.css

1529 ms

nicepage.css

nicepage.css

1720 ms

media.css

media.css

1735 ms

fonts_743.css

fonts_743.css

1738 ms

woocommerce-np-styles.css

woocommerce-np-styles.css

1739 ms

jquery.min.js

jquery.min.js

1747 ms

jquery-migrate.min.js

jquery-migrate.min.js

1755 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1937 ms

js

js

78 ms

css

css

28 ms

api.js

api.js

35 ms

fonts.css

fonts.css

1517 ms

wc-blocks.css

wc-blocks.css

1302 ms

add-to-cart.min.js

add-to-cart.min.js

1302 ms

js.cookie.min.js

js.cookie.min.js

1309 ms

woocommerce.min.js

woocommerce.min.js

1311 ms

um-gdpr.min.js

um-gdpr.min.js

1504 ms

nicepage.js

nicepage.js

1949 ms

woocommerce-np-scripts.js

woocommerce-np-scripts.js

1304 ms

hooks.min.js

hooks.min.js

1304 ms

i18n.min.js

i18n.min.js

1310 ms

index.js

index.js

1310 ms

index.js

index.js

1503 ms

front.js

front.js

1307 ms

sourcebuster.min.js

sourcebuster.min.js

1310 ms

order-attribution.min.js

order-attribution.min.js

1311 ms

index.js

index.js

1313 ms

wp-polyfill.min.js

wp-polyfill.min.js

1510 ms

index.js

index.js

1513 ms

underscore.min.js

underscore.min.js

1314 ms

wp-util.min.js

wp-util.min.js

1311 ms

tipsy.min.js

tipsy.min.js

1314 ms

um-confirm.min.js

um-confirm.min.js

1623 ms

picker.min.js

picker.min.js

1614 ms

picker.date.min.js

picker.date.min.js

1421 ms

picker.time.min.js

picker.time.min.js

1415 ms

common.min.js

common.min.js

1413 ms

cropper.min.js

cropper.min.js

1556 ms

common-frontend.min.js

common-frontend.min.js

1607 ms

um-modal.min.js

um-modal.min.js

1607 ms

jquery-form.min.js

jquery-form.min.js

1400 ms

fileupload.js

fileupload.js

1397 ms

um-functions.min.js

um-functions.min.js

1388 ms

um-responsive.min.js

um-responsive.min.js

1490 ms

um-conditional.min.js

um-conditional.min.js

1587 ms

select2.full.min.js

select2.full.min.js

1576 ms

en.js

en.js

1406 ms

um-raty.min.js

um-raty.min.js

1417 ms

um-scripts.min.js

um-scripts.min.js

1401 ms

um-profile.min.js

um-profile.min.js

1508 ms

um-account.min.js

um-account.min.js

1603 ms

universal.js

universal.js

147 ms

sbi-sprite.png

sbi-sprite.png

706 ms

3139283.png

3139283.png

704 ms

ed3a066c-ed16-4323-90f8-29aa76087bcb.png

ed3a066c-ed16-4323-90f8-29aa76087bcb.png

273 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

147 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

147 ms

S6u8w4BMUTPHh30AXC-s.woff

S6u8w4BMUTPHh30AXC-s.woff

214 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

214 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

215 ms

OldClaudeLPRegular.ttf

OldClaudeLPRegular.ttf

1094 ms

OldStandard-Regular.ttf

OldStandard-Regular.ttf

797 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

217 ms

Accessibility Review

dirtyjanes.com accessibility score

81

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

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

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.

Best Practices

dirtyjanes.com best practices score

92

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

SEO Factors

dirtyjanes.com SEO score

86

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

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

dirtyjanes.com

Open Graph data is detected on the main page of Dirty Janes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: