Report Summary

  • 0

    Performance

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

pfhoo.com

批发户_跨境电商_珠宝首饰_外贸饰品_首饰批发_纯银批发_饰品批发网_跨境首饰货源_水晶手链_亚马逊选品_黄金戒指_珍珠耳环_项链批发

Page Load Speed

50.1 sec in total

First Response

1.6 sec

Resources Loaded

47.7 sec

Page Rendered

782 ms

About Website

Welcome to pfhoo.com homepage info - get ready to check Pfhoo best content for China right away, or after learning these important things about pfhoo.com

12年专注于时尚珠宝首饰,首饰品牌,黄金首饰,首饰设计,外贸饰品货源网,首饰盒,跨境首饰货源,奢饰品,水晶手链,珍珠手链,纯银手链,石榴石手链,铂金项链,四叶草项链,戒指的戴法和意义,珍珠耳环,亚马逊选品,一件代发,一件代发货源,一件代发货源网.跨境电商,纯银批发,手链,饰品批发,首饰批发,饰品批发网,饰品,手链批发,项链,黄金项链,外贸饰品,戒指,黄金手链,黄金戒指,铂金戒指,珍珠项链,耳环,项...

Visit pfhoo.com

Key Findings

We analyzed Pfhoo.com page load time and found that the first response time was 1.6 sec and then it took 48.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

pfhoo.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value27.6 s

0/100

25%

SI (Speed Index)

Value45.2 s

0/100

10%

TBT (Total Blocking Time)

Value21,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.413

0/100

15%

TTI (Time to Interactive)

Value37.6 s

0/100

10%

Network Requests Diagram

pfhoo.com

1631 ms

www.pfhoo.com

15614 ms

global.css

2643 ms

jquery-1.7.1.min.js

8918 ms

common.js

2214 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 59% of them (64 requests) were addressed to the original Pfhoo.com, 19% (21 requests) were made to Image.pfhoo.com and 14% (15 requests) were made to Img.inalis.com. The less responsive or slowest element that took the longest time to load (22.6 sec) belongs to the original domain Pfhoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 632.0 kB (33%)

Content Size

1.9 MB

After Optimization

1.3 MB

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

HTML Optimization

-82%

Potential reduce by 94.9 kB

  • Original 116.0 kB
  • After minification 86.4 kB
  • After compression 21.2 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 29.7 kB, which is 26% 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 94.9 kB or 82% of the original size.

Image Optimization

-26%

Potential reduce by 432.5 kB

  • Original 1.7 MB
  • After minification 1.2 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, Pfhoo needs image optimization as it can save up to 432.5 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 58.1 kB

  • Original 83.0 kB
  • After minification 68.5 kB
  • After compression 24.9 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 58.1 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 46.5 kB

  • Original 54.1 kB
  • After minification 33.5 kB
  • After compression 7.5 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. Pfhoo.com needs all CSS files to be minified and compressed as it can save up to 46.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (12%)

Requests Now

105

After Optimization

92

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

Accessibility Review

pfhoo.com accessibility score

45

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

Image elements do not have [alt] attributes

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

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

robots.txt is not valid

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 Pfhoo.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 Pfhoo.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 Pfhoo. 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: