Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 70

    SEO

    Google-friendlier than
    29% of websites

tilearchive.com

Search for old and new tiles | tile archive | wall and floor tile search engine.

Page Load Speed

3.7 sec in total

First Response

1.4 sec

Resources Loaded

2.2 sec

Page Rendered

76 ms

tilearchive.com screenshot

About Website

Welcome to tilearchive.com homepage info - get ready to check Tile Archive best content right away, or after learning these important things about tilearchive.com

Find new or old tiles in our archive. Search for FREE through worldwide tile manufacturers & their tile ranges including borders, trims, edging and tiling accessories.

Visit tilearchive.com

Key Findings

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

Performance Metrics

tilearchive.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.341

33/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

tilearchive.com

1372 ms

tilearchive.com

314 ms

bridge-tag.css

76 ms

jquery.min.js

9 ms

m-resp.css

152 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 77% of them (23 requests) were addressed to the original Tilearchive.com, 7% (2 requests) were made to Google.com and 7% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Tilearchive.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.2 kB (8%)

Content Size

131.7 kB

After Optimization

121.5 kB

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

HTML Optimization

-73%

Potential reduce by 7.4 kB

  • Original 10.1 kB
  • After minification 8.7 kB
  • After compression 2.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 1.4 kB, which is 14% 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 7.4 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.6 kB
  • After minification 1.6 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. Tile Archive images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 564 B

  • Original 108.0 kB
  • After minification 108.0 kB
  • After compression 107.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

-18%

Potential reduce by 2.2 kB

  • Original 12.0 kB
  • After minification 12.0 kB
  • After compression 9.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. Tilearchive.com needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 18% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

13

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

Accessibility Review

tilearchive.com accessibility score

62

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

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

tilearchive.com best practices score

58

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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

tilearchive.com SEO score

70

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tilearchive.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tilearchive.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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