Access xohlar.com. xohlar.com

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

index.php

726 ms

style_v2b.css

258 ms

bottom_pop.css

148 ms

tj.js

151 ms

js-sdk-pro.min.js

8 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 65% of them (83 requests) were addressed to the original Xohlar.com, 31% (39 requests) were made to Itavcn.com and 1% (1 request) were made to Sdk.51.la. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Itavcn.com.

Content Size

1.4 MB

After Optimization

1.2 MB

In fact, the total size of Xohlar.com main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 228.1 kB

Original 289.0 kB
After minification 266.2 kB
After compression 60.9 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 228.1 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 13.7 kB

Original 1.1 MB
After minification 1.1 MB

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. Xohlar images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 74 B

Original 444 B
After minification 434 B
After compression 370 B

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

CSS Optimization

-35%

Potential reduce by 2.0 kB

Original 5.6 kB
After minification 5.5 kB
After compression 3.7 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. Xohlar.com needs all CSS files to be minified and compressed as it can save up to 2.0 kB or 35% of the original size.

Requests Now

122

After Optimization

102

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

High

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These are opportunities to improve keyboard navigation in your application.

High

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

High

Heading elements are not in a sequentially-descending order

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

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xohlar.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 Xohlar.com main page’s claimed encoding is gbk. 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

xohlar.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

xohlar.com

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

index.php

style_v2b.css

bottom_pop.css

tj.js

js-sdk-pro.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

index.php

style_v2b.css

bottom_pop.css

tj.js

js-sdk-pro.min.js

collect

gx_mfzcsg_03.jpg

z_navlogo_03.jpg

pa

z_xinnavshouye_03.jpg

notice_new.gif

vissonic.gif

itavcnad.gif

lixun.jpg

kj248x58.gif

rc.gif

sw%20banner.jpg

720x68.jpg

720x68.jpg

youpai300x30.jpg

3_1.jpg

Untitled-1.jpg

11.jpg

2.jpg

sanxing.jpg

143-60-button.gif

lcf1%20(2).gif

kxwell.gif

bxl143.jpg

senran02.gif

bj.jpg

ad_rili20130104.jpg

ad_xinyi20130104.jpg

a_plmx0802.gif

ad_lanpu20120104.jpg

ad_shae20130104.jpg

ad_hongz20120104.jpg

ad_sony20130104.jpg

reac20120713.gif

2022072809411831.jpg

chunzhong.gif

2022053109201978.png

2022040210223588.jpg