Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

timewasantiques.net

Time Was Antiques

Page Load Speed

1.9 sec in total

First Response

541 ms

Resources Loaded

1.1 sec

Page Rendered

320 ms

timewasantiques.net screenshot

About Website

Click here to check amazing Time Was Antiques content. Otherwise, check out these important facts you probably never knew about timewasantiques.net

Antiques, collectibles, quality items for the home. Most with a British accent

Visit timewasantiques.net

Key Findings

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

Performance Metrics

timewasantiques.net performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.184

66/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

timewasantiques.net

541 ms

store.css

142 ms

javascript-api.js

26 ms

twitter.js

168 ms

si.js

74 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 24% of them (13 requests) were addressed to the original Timewasantiques.net, 53% (29 requests) were made to Tias.com and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (541 ms) belongs to the original domain Timewasantiques.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 230.9 kB (41%)

Content Size

568.6 kB

After Optimization

337.7 kB

In fact, the total size of Timewasantiques.net main page is 568.6 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. 20% of websites need less resources to load. Images take 316.9 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 193.4 kB

  • Original 221.2 kB
  • After minification 216.5 kB
  • After compression 27.8 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 193.4 kB or 87% of the original size.

Image Optimization

-10%

Potential reduce by 31.4 kB

  • Original 316.9 kB
  • After minification 285.5 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. Time Was Antiques images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 2.4 kB

  • Original 26.1 kB
  • After minification 25.5 kB
  • After compression 23.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

-84%

Potential reduce by 3.7 kB

  • Original 4.4 kB
  • After minification 3.3 kB
  • After compression 701 B

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. Timewasantiques.net needs all CSS files to be minified and compressed as it can save up to 3.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (19%)

Requests Now

53

After Optimization

43

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Time Was Antiques. 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 as a result speed up the page load time.

Accessibility Review

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

button, link, and menuitem elements do not have accessible names.

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

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

timewasantiques.net best practices score

75

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

High

Page has valid source maps

SEO Factors

timewasantiques.net SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Timewasantiques.net 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 Timewasantiques.net main page’s claimed encoding is iso-8859-1. 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 Time Was Antiques. 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: