Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

phonakhearingaidsz.com

世搏体育APP(中国)有限公司

Page Load Speed

25.6 sec in total

First Response

923 ms

Resources Loaded

24.3 sec

Page Rendered

444 ms

phonakhearingaidsz.com screenshot

About Website

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

世搏体育APP(中国)有限公司坐落在全国改革开放的窗口深圳(光明新区),成立于2006年1月,主要从事建设领域新技术、新工艺、新材料的科学研究和技术服务工作,是集科研、技术服务与咨询、新材料研发等于一体的综合性科研单位。

Visit phonakhearingaidsz.com

Key Findings

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

Performance Metrics

phonakhearingaidsz.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,720 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

phonakhearingaidsz.com

923 ms

phonakhearingaidsz.com

857 ms

www.phonakhearingaidsz.com

412 ms

www.phonakhearingaidsz.com

1024 ms

ky.js

1241 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 47% of them (34 requests) were addressed to the original Phonakhearingaidsz.com, 16% (12 requests) were made to Webpage.qidian.qq.com and 11% (8 requests) were made to Bqq.gtimg.com. The less responsive or slowest element that took the longest time to load (17.2 sec) relates to the external source Jbwzzzjs.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 404.4 kB (13%)

Content Size

3.2 MB

After Optimization

2.8 MB

In fact, the total size of Phonakhearingaidsz.com main page is 3.2 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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 14.8 kB

  • Original 21.1 kB
  • After minification 21.0 kB
  • After compression 6.3 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 14.8 kB or 70% of the original size.

Image Optimization

-11%

Potential reduce by 294.3 kB

  • Original 2.6 MB
  • After minification 2.3 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. Obviously, Phonakhearingaidsz needs image optimization as it can save up to 294.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 89.9 kB

  • Original 393.0 kB
  • After minification 390.3 kB
  • After compression 303.1 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 89.9 kB or 23% of the original size.

CSS Optimization

-4%

Potential reduce by 5.4 kB

  • Original 120.0 kB
  • After minification 119.7 kB
  • After compression 114.6 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. Phonakhearingaidsz.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

65

After Optimization

35

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

Accessibility Review

phonakhearingaidsz.com accessibility score

42

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.

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

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

phonakhearingaidsz.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

phonakhearingaidsz.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phonakhearingaidsz.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Phonakhearingaidsz.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

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