Tools & Wizards About Us
en.yeahmobi.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

en.yeahmobi.com

International Leading Digital Service Provider|Yeahmobi

Page Load Speed

6.8 sec in total

First Response

456 ms

Resources Loaded

6 sec

Page Rendered

335 ms

en.yeahmobi.com screenshot

About Website

Visit en.yeahmobi.com now to see the best up-to-date En Yeahmobi content for Hong Kong and also check out these interesting facts you probably never knew about en.yeahmobi.com

Driven by big data and AI, Yeahmobi is an intelligent marketing service provider committed to help companies expand global market. Through our comprehensive one-stop service empowered by performance m...

Visit en.yeahmobi.com

Key Findings

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

Performance Metrics

en.yeahmobi.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value12.1 s

4/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

en.yeahmobi.com

456 ms

en.yeahmobi.com

1540 ms

j_animate.css

491 ms

bootstrap.min.css

1264 ms

owl.carousel.css

637 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 96% of them (75 requests) were addressed to the original En.yeahmobi.com, 3% (2 requests) were made to Hm.baidu.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain En.yeahmobi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (63%)

Content Size

1.8 MB

After Optimization

662.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of En.yeahmobi.com main page is 1.8 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. 50% of websites need less resources to load. Images take 775.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 47.2 kB

  • Original 56.0 kB
  • After minification 45.3 kB
  • After compression 8.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 10.7 kB, which is 19% 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 47.2 kB or 84% of the original size.

Image Optimization

-43%

Potential reduce by 334.8 kB

  • Original 775.8 kB
  • After minification 441.0 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, En Yeahmobi needs image optimization as it can save up to 334.8 kB or 43% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 393.4 kB

  • Original 545.8 kB
  • After minification 544.3 kB
  • After compression 152.4 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 393.4 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 348.5 kB

  • Original 408.4 kB
  • After minification 394.2 kB
  • After compression 59.9 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. En.yeahmobi.com needs all CSS files to be minified and compressed as it can save up to 348.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (30%)

Requests Now

73

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en.yeahmobi.com

en.yeahmobi.com

456 ms

en.yeahmobi.com

en.yeahmobi.com

1540 ms

j_animate.css

j_animate.css

491 ms

bootstrap.min.css

bootstrap.min.css

1264 ms

owl.carousel.css

owl.carousel.css

637 ms

owl.theme.css

owl.theme.css

1287 ms

style.css

style.css

1075 ms

media.css

media.css

654 ms

jquery.min.js

jquery.min.js

920 ms

bootstrap.min.js

bootstrap.min.js

1056 ms

j_animate.js

j_animate.js

872 ms

owl.carousel.js

owl.carousel.js

1325 ms

slick.js

slick.js

1137 ms

jquery.cookie.js

jquery.cookie.js

1271 ms

lottie-player.js

lottie-player.js

1934 ms

jquery.superslide.2.1.1.js

jquery.superslide.2.1.1.js

1201 ms

jquery.paroller.js

jquery.paroller.js

1207 ms

EasyLazyload.min.js

EasyLazyload.min.js

1211 ms

j_web.js

j_web.js

1232 ms

gtm.js

gtm.js

153 ms

logo-yeahmobi.svg

logo-yeahmobi.svg

225 ms

nav_ico_right.svg

nav_ico_right.svg

323 ms

c9f7c06f22.png

c9f7c06f22.png

354 ms

afd36e500b.png

afd36e500b.png

357 ms

6f69c3813d.png

6f69c3813d.png

383 ms

88eadf9480.png

88eadf9480.png

445 ms

e9f3312623.png

e9f3312623.png

539 ms

2b58b966cd.png

2b58b966cd.png

565 ms

51e28c606f.png

51e28c606f.png

568 ms

b8100706fa.png

b8100706fa.png

598 ms

e6365adcf8.png

e6365adcf8.png

720 ms

0f8c764fce.png

0f8c764fce.png

808 ms

eafe3af969.png

eafe3af969.png

809 ms

e94c89c261.png

e94c89c261.png

809 ms

42ae3cebe4.png

42ae3cebe4.png

818 ms

937fc2ff6c.png

937fc2ff6c.png

817 ms

5fb3f1cd52.png

5fb3f1cd52.png

884 ms

4946ffb215.png

4946ffb215.png

971 ms

22f3f337e0.png

22f3f337e0.png

988 ms

de393b4a8c.png

de393b4a8c.png

993 ms

64b1bacdc6.png

64b1bacdc6.png

1031 ms

0199060dec.png

0199060dec.png

1031 ms

e70668ffd5.png

e70668ffd5.png

1106 ms

c71fd7910b.png

c71fd7910b.png

1187 ms

bf53ade1b4.png

bf53ade1b4.png

1201 ms

bea1d62593.png

bea1d62593.png

1203 ms

6f7ebe791f.png

6f7ebe791f.png

1249 ms

e00e13eeed.png

e00e13eeed.png

1249 ms

8e53f382b6.png

8e53f382b6.png

1324 ms

98b0404dfd.png

98b0404dfd.png

1404 ms

efe5ccd9f5.png

efe5ccd9f5.png

1310 ms

SF-Pro-Text-Regular.otf

SF-Pro-Text-Regular.otf

1926 ms

SF-Pro-Text-Medium.otf

SF-Pro-Text-Medium.otf

1590 ms

SF-Pro-Text-Semibold.otf

SF-Pro-Text-Semibold.otf

1537 ms

1a7718b6be.png

1a7718b6be.png

1381 ms

8975db03c5.png

8975db03c5.png

1397 ms

7d7252c9e0.png

7d7252c9e0.png

1304 ms

80ca9d2fdf.png

80ca9d2fdf.png

1432 ms

64eec19951.png

64eec19951.png

1484 ms

0f6cc40adc.png

0f6cc40adc.png

1457 ms

0fdbfbcd89.png

0fdbfbcd89.png

1457 ms

facebook.svg

facebook.svg

1364 ms

twitter.svg

twitter.svg

1421 ms

linkedin.svg

linkedin.svg

1515 ms

report_download.svg

report_download.svg

1487 ms

bg01.svg

bg01.svg

1471 ms

hm.js

hm.js

1408 ms

index.php

index.php

1441 ms

right_iphone_frame.png

right_iphone_frame.png

1403 ms

cube01.png

cube01.png

1453 ms

cube02.png

cube02.png

1455 ms

cube03.svg

cube03.svg

1456 ms

link-arrow-yellowcopy.svg

link-arrow-yellowcopy.svg

1515 ms

cube04.svg

cube04.svg

1522 ms

bg02.png

bg02.png

1893 ms

users.svg

users.svg

1484 ms

hm.gif

hm.gif

313 ms

income.svg

income.svg

217 ms

Accessibility Review

en.yeahmobi.com accessibility score

48

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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.

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

en.yeahmobi.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

en.yeahmobi.com SEO score

68

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise En.yeahmobi.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that En.yeahmobi.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

en.yeahmobi.com

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