Tools & Wizards About Us
selector.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

selector.com

Selector – building, architecture, design and landscape products and news.

Page Load Speed

5.4 sec in total

First Response

399 ms

Resources Loaded

4.7 sec

Page Rendered

223 ms

selector.com screenshot

About Website

Click here to check amazing Selector content for Australia. Otherwise, check out these important facts you probably never knew about selector.com

Find products for architecture, interior, building and landscape. Products with inspiring images and detailed information.

Visit selector.com

Key Findings

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

Performance Metrics

selector.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value550 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

selector.com

399 ms

selector.com

807 ms

969 ms

output.e2a2e03d463a.css

1204 ms

modernizr-2.8.3-respond-1.4.2.min.js

820 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Selector.com, 32% (13 requests) were made to Media.architectureau.com and 15% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Media.architectureau.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.3 kB (20%)

Content Size

412.2 kB

After Optimization

330.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Selector.com main page is 412.2 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. 45% of websites need less resources to load. Javascripts take 188.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 72.0 kB

  • Original 84.6 kB
  • After minification 71.6 kB
  • After compression 12.7 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 13.0 kB, which is 15% 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 72.0 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 1.8 kB

  • Original 76.9 kB
  • After minification 75.1 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. Selector images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 7.5 kB

  • Original 188.8 kB
  • After minification 188.8 kB
  • After compression 181.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 48 B

  • Original 61.9 kB
  • After minification 61.8 kB
  • After compression 61.8 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. Selector.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (50%)

Requests Now

28

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

selector.com

selector.com

399 ms

selector.com

selector.com

807 ms

969 ms

output.e2a2e03d463a.css

output.e2a2e03d463a.css

1204 ms

modernizr-2.8.3-respond-1.4.2.min.js

modernizr-2.8.3-respond-1.4.2.min.js

820 ms

js

js

55 ms

dop2lvc.css

dop2lvc.css

77 ms

player.js

player.js

51 ms

output.10734307113c.js

output.10734307113c.js

1266 ms

lazysizes.min.js

lazysizes.min.js

834 ms

output.e57c4a1d0e4d.js

output.e57c4a1d0e4d.js

837 ms

2138884.js

2138884.js

61 ms

atrk.js

atrk.js

26 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

51 ms

insight.min.js

insight.min.js

42 ms

p.css

p.css

63 ms

aau-smal-spaced.svg

aau-smal-spaced.svg

317 ms

368x245.png

368x245.png

317 ms

analytics.js

analytics.js

116 ms

js

js

115 ms

insight_tag_errors.gif

insight_tag_errors.gif

534 ms

489ec5c87edee041c53a0fab954149d6.jpg

489ec5c87edee041c53a0fab954149d6.jpg

1256 ms

institutes.svg

institutes.svg

239 ms

selector-logo.svg

selector-logo.svg

236 ms

hearts.svg

hearts.svg

238 ms

fbevents.js

fbevents.js

218 ms

d

d

119 ms

d

d

149 ms

d

d

177 ms

d

d

192 ms

d

d

177 ms

fa-solid-900.woff

fa-solid-900.woff

415 ms

fa-regular-400.woff

fa-regular-400.woff

961 ms

fa-light-300.woff

fa-light-300.woff

972 ms

fa-brands-400.woff

fa-brands-400.woff

573 ms

banner.js

banner.js

241 ms

2138884.js

2138884.js

268 ms

collect

collect

175 ms

collect

collect

73 ms

embed.js

embed.js

53 ms

ga-audiences

ga-audiences

30 ms

Accessibility Review

selector.com accessibility score

80

Accessibility Issues

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.

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

selector.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

selector.com SEO score

89

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

selector.com

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