Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

attic.city

Furniture, Decor and Fashion from Small Stores | ATTIC Local Search

Page Load Speed

820 ms in total

First Response

37 ms

Resources Loaded

633 ms

Page Rendered

150 ms

About Website

Visit attic.city now to see the best up-to-date ATTIC content for United States and also check out these interesting facts you probably never knew about attic.city

ATTIC is a search engine to help you find vintage and modern furniture, home decor and clothing from small stores, boutiques, designers and artists.

Visit attic.city

Key Findings

We analyzed Attic.city page load time and found that the first response time was 37 ms and then it took 783 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

attic.city performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value3.3 s

93/100

10%

Network Requests Diagram

attic.city

37 ms

styles.css

23 ms

jquery.typeahead.min.css

36 ms

plausible.js

19 ms

jquery.min.js

52 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 80% of them (16 requests) were addressed to the original Attic.city, 5% (1 request) were made to Plausible.io and 5% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (559 ms) relates to the external source Imagedelivery.net.

Page Optimization Overview & Recommendations

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

Content Size

224.2 kB

After Optimization

206.8 kB

In fact, the total size of Attic.city main page is 224.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. 35% of websites need less resources to load. Images take 146.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 17.3 kB

  • Original 22.7 kB
  • After minification 22.7 kB
  • After compression 5.4 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 17.3 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 146.8 kB
  • After minification 146.8 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. ATTIC images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 47 B

  • Original 26.9 kB
  • After minification 26.9 kB
  • After compression 26.9 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 10 B

  • Original 27.8 kB
  • After minification 27.8 kB
  • After compression 27.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. Attic.city has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (35%)

Requests Now

17

After Optimization

11

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

Accessibility Review

attic.city accessibility score

98

Accessibility Issues

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

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

attic.city SEO score

100

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

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