Tools & Wizards About Us
puffery.info screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

puffery.info

Hong Kong's Financial Hub Will Lose Business to Singapore on China Law

Page Load Speed

11.9 sec in total

First Response

270 ms

Resources Loaded

11.3 sec

Page Rendered

279 ms

puffery.info screenshot

About Website

Click here to check amazing Puffery content for Russia. Otherwise, check out these important facts you probably never knew about puffery.info

Singapore was the world's 5th largest financial centre in 2020, but analysts think Singapore could boost its global standing if firms leave Hong Kong.

Visit puffery.info

Key Findings

We analyzed Puffery.info page load time and found that the first response time was 270 ms and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

puffery.info performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value79.4 s

0/100

25%

SI (Speed Index)

Value88.1 s

0/100

10%

TBT (Total Blocking Time)

Value108,170 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value135.5 s

0/100

10%

Network Requests Diagram

puffery.info

270 ms

a

132 ms

140 ms

bootstrap.min.css

382 ms

style.css

276 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 40% of them (18 requests) were addressed to the original Puffery.info, 16% (7 requests) were made to Translate.googleapis.com and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (10.1 sec) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 363.3 kB (31%)

Content Size

1.2 MB

After Optimization

791.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Puffery.info main page is 1.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. 40% of websites need less resources to load. Images take 581.7 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 11.2 kB

  • Original 16.4 kB
  • After minification 14.3 kB
  • After compression 5.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 2.1 kB, which is 13% 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 11.2 kB or 68% of the original size.

Image Optimization

-1%

Potential reduce by 7.4 kB

  • Original 581.7 kB
  • After minification 574.3 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. Puffery images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 242.4 kB

  • Original 429.7 kB
  • After minification 429.7 kB
  • After compression 187.3 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 242.4 kB or 56% of the original size.

CSS Optimization

-81%

Potential reduce by 102.3 kB

  • Original 126.5 kB
  • After minification 125.6 kB
  • After compression 24.2 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. Puffery.info needs all CSS files to be minified and compressed as it can save up to 102.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (54%)

Requests Now

37

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puffery. 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.

Network Requests Diagram

puffery.info

puffery.info

270 ms

a

a

132 ms

140 ms

bootstrap.min.css

bootstrap.min.css

382 ms

style.css

style.css

276 ms

css

css

40 ms

element.js

element.js

37 ms

jquery.min.js

jquery.min.js

34 ms

bootstrap.min.js

bootstrap.min.js

280 ms

gtm.js

gtm.js

83 ms

main-bg.jpg

main-bg.jpg

751 ms

logo.png

logo.png

253 ms

bottom-icon.png

bottom-icon.png

255 ms

translateelement.css

translateelement.css

21 ms

main.js

main.js

77 ms

star.png

star.png

268 ms

input-icon-2.png

input-icon-2.png

265 ms

content-bg.jpg

content-bg.jpg

631 ms

logo_icon.png

logo_icon.png

447 ms

icon_1.png

icon_1.png

457 ms

icon_2.png

icon_2.png

506 ms

icon_3.png

icon_3.png

515 ms

arrows.png

arrows.png

693 ms

list-icon.png

list-icon.png

705 ms

RjgO7rYTmqiVp7vzi-Q5UT8E0i7KZn-EPnyo3HZu7kw.woff

RjgO7rYTmqiVp7vzi-Q5UT8E0i7KZn-EPnyo3HZu7kw.woff

20 ms

DXI1ORHCpsQm3Vp6mXoaTYraN7vELC11_xip9Rz-hMs.woff

DXI1ORHCpsQm3Vp6mXoaTYraN7vELC11_xip9Rz-hMs.woff

20 ms

MTP_ySUJH_bn48VBG8sNSoraN7vELC11_xip9Rz-hMs.woff

MTP_ySUJH_bn48VBG8sNSoraN7vELC11_xip9Rz-hMs.woff

21 ms

k3k702ZOKiLJc3WVjuplzIraN7vELC11_xip9Rz-hMs.woff

k3k702ZOKiLJc3WVjuplzIraN7vELC11_xip9Rz-hMs.woff

20 ms

element_main.js

element_main.js

42 ms

analytics.js

analytics.js

12 ms

watch.js

watch.js

198 ms

fbds.js

fbds.js

26 ms

rtrg

rtrg

273 ms

code.js

code.js

274 ms

collect

collect

30 ms

168 ms

translate_24dp.png

translate_24dp.png

53 ms

l

l

54 ms

cleardot.gif

cleardot.gif

91 ms

googlelogo_color_68x28dp.png

googlelogo_color_68x28dp.png

5 ms

loading.gif

loading.gif

12 ms

te_ctrl3.gif

te_ctrl3.gif

20 ms

te_bk.gif

te_bk.gif

10 ms

watch.js

watch.js

10052 ms

counter

counter

133 ms

Accessibility Review

puffery.info accessibility score

92

Accessibility Issues

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

puffery.info best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

puffery.info SEO score

92

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puffery.info 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 Puffery.info 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

puffery.info

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