Tools & Wizards About Us
tayse.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

tayse.com

TAYSE RUGS | Area Rug Wholesaler and Distributor

Page Load Speed

1.5 sec in total

First Response

317 ms

Resources Loaded

941 ms

Page Rendered

217 ms

tayse.com screenshot

About Website

Welcome to tayse.com homepage info - get ready to check TAYSE best content for United States right away, or after learning these important things about tayse.com

TAYSE RUGS, area rug wholesaler and distributor. Visit our online rug gallery to see beautiful machine made rugs.

Visit tayse.com

Key Findings

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

Performance Metrics

tayse.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.535

14/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

tayse.com

317 ms

jquery-1.4.3.min.js

243 ms

jquery.fancybox-1.3.4.js

190 ms

main.css

134 ms

jquery.fancybox-1.3.4.css

133 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that all of those requests were addressed to Tayse.com and no external sources were called. The less responsive or slowest element that took the longest time to load (317 ms) belongs to the original domain Tayse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.0 kB (34%)

Content Size

343.1 kB

After Optimization

228.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tayse.com main page is 343.1 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. Only 10% of websites need less resources to load. Images take 206.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 7.1 kB

  • Original 9.9 kB
  • After minification 8.8 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 1.1 kB, which is 11% 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.1 kB or 72% of the original size.

Image Optimization

-9%

Potential reduce by 18.4 kB

  • Original 206.7 kB
  • After minification 188.4 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. TAYSE images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 73.3 kB

  • Original 106.0 kB
  • After minification 99.1 kB
  • After compression 32.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 73.3 kB or 69% of the original size.

CSS Optimization

-80%

Potential reduce by 16.3 kB

  • Original 20.4 kB
  • After minification 15.6 kB
  • After compression 4.2 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. Tayse.com needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 80% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TAYSE. According to our analytics all requests are already optimized.

Network Requests Diagram

tayse.com

tayse.com

317 ms

jquery-1.4.3.min.js

jquery-1.4.3.min.js

243 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

190 ms

main.css

main.css

134 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

133 ms

900.css

900.css

71 ms

bg_pattern.jpg

bg_pattern.jpg

72 ms

rotate.php

rotate.php

250 ms

excel.png

excel.png

80 ms

pdf.png

pdf.png

70 ms

word.png

word.png

139 ms

footer_bg.jpg

footer_bg.jpg

138 ms

email.png

email.png

138 ms

phone.png

phone.png

138 ms

Tayse_Logo.jpg

Tayse_Logo.jpg

146 ms

side_nav_bg_900.jpg

side_nav_bg_900.jpg

161 ms

search.jpg

search.jpg

163 ms

search_icon.jpg

search_icon.jpg

161 ms

new.png

new.png

169 ms

Gotham.woff

Gotham.woff

223 ms

Lovelo.woff

Lovelo.woff

228 ms

Accessibility Review

tayse.com accessibility score

66

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.

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

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

SEO Factors

tayse.com SEO score

92

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tayse.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 Tayse.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

tayse.com

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