Report Summary

  • 0

    Performance

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

torontoemporium.com

lehu88日韩国产无码_秋葵视频无限次数安卓下载_99RE6在线热播精品免费_中文字幕在线永久播放

Page Load Speed

3.3 sec in total

First Response

352 ms

Resources Loaded

2.9 sec

Page Rendered

55 ms

torontoemporium.com screenshot

About Website

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

lehu88日韩国产无码_秋葵视频无限次数安卓下载_99RE6在线热播精品免费_中文字幕在线永久播放_往下边塞玉器骑马_女人的地男人犁_freeⅹ性欧美xvideos_www.torontoemporium.com

Visit torontoemporium.com

Key Findings

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

Performance Metrics

torontoemporium.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

index.php

352 ms

push.js

431 ms

common.js

64 ms

tj.js

127 ms

0.gif

45 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 30% of them (3 requests) were addressed to the original Torontoemporium.com, 40% (4 requests) were made to Hm.baidu.com and 20% (2 requests) were made to Sstatic1.histats.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Hm.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 kB (21%)

Content Size

6.2 kB

After Optimization

4.9 kB

In fact, the total size of Torontoemporium.com main page is 6.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 4.9 kB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 663 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 630 B

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 663 B or 51% of the original size.

JavaScript Optimization

-13%

Potential reduce by 652 B

  • Original 4.9 kB
  • After minification 4.8 kB
  • After compression 4.2 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 652 B or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (44%)

Requests Now

9

After Optimization

5

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

Accessibility Review

torontoemporium.com accessibility score

50

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

<frame> or <iframe> elements do not have a title

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

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

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

torontoemporium.com SEO score

92

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torontoemporium.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Torontoemporium.com main page’s claimed encoding is gb2312. 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 Torontoemporium. 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: