2.9 sec in total
267 ms
2.4 sec
224 ms
Click here to check amazing Yi content. Otherwise, check out these important facts you probably never knew about yi.sg
Visit yi.sgWe analyzed Yi.sg page load time and found that the first response time was 267 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
yi.sg performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value2.7 s
86/100
25%
Value3.2 s
92/100
10%
Value60 ms
100/100
30%
Value0.566
12/100
15%
Value5.1 s
75/100
10%
267 ms
249 ms
189 ms
175 ms
166 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 99% of them (67 requests) were addressed to the original Yi.sg, 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Yi.sg.
Page size can be reduced by 491.5 kB (31%)
1.6 MB
1.1 MB
In fact, the total size of Yi.sg main page is 1.6 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. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 34.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 5.9 kB, which is 14% 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 34.8 kB or 82% of the original size.
Potential reduce by 138.7 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. Obviously, Yi needs image optimization as it can save up to 138.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 238.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 238.2 kB or 67% of the original size.
Potential reduce by 79.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. Yi.sg needs all CSS files to be minified and compressed as it can save up to 79.8 kB or 87% of the original size.
Number of requests can be reduced by 18 (28%)
64
46
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
yi.sg
267 ms
style.css
249 ms
drop-down.css
189 ms
latest-promotion.css
175 ms
services-features.css
166 ms
style3.css
206 ms
animate.css
343 ms
liquid-slider.css
287 ms
jquery-1.8.2.min.js
437 ms
jquery.min.js
6 ms
jquery.easing.1.3.js
319 ms
jquery.touchSwipe.min.js
283 ms
jquery.liquid-slider-custom.min.js
374 ms
latest-promotion.js
400 ms
latest-promotion%202.js
580 ms
jquery.js
604 ms
jquery_002.js
436 ms
script.js
494 ms
services-slide.css
475 ms
middel-script.js
458 ms
middel-script2.js
486 ms
img1.png
159 ms
development-serv.png
329 ms
learn%20more-banner.png
174 ms
img2.png
194 ms
hosting.png
382 ms
img3.png
248 ms
vps-deicated-servr.png
430 ms
img4.png
263 ms
brand-management.png
436 ms
img55.png
331 ms
coprate-services.png
576 ms
img6.png
436 ms
internet-social.png
594 ms
img7.png
456 ms
social-market.png
666 ms
img5.png
525 ms
virtual-resource.png
664 ms
banner-shadow.png
577 ms
learn%20more.png
605 ms
arrow-l.png
675 ms
arrow-r.png
667 ms
horizontal.png
673 ms
web-dep.jpg
783 ms
soft-ware.jpg
904 ms
web-dep.png
871 ms
vps-deicated.png
866 ms
live%20streem.jpg
907 ms
inter-adver.png
916 ms
top.html
865 ms
header.html
1462 ms
logo.html
1416 ms
social-marketing.png
1511 ms
business-consultny.png
1506 ms
logobackground.jpg
1463 ms
menu.png
1271 ms
arrow-up.jpg
1395 ms
arrow-down.jpg
1400 ms
loading.gif
1357 ms
background.png
1426 ms
bottom-bar.html
1397 ms
footer.html
1441 ms
copyright.html
1332 ms
fb.jpg
244 ms
twitter.jpg
244 ms
logo.png
247 ms
message.png
86 ms
dot.png
38 ms
yi.sg accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
yi.sg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
yi.sg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yi.sg 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 Yi.sg 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.
yi.sg
Open Graph description is not detected on the main page of Yi. 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: