Tools & Wizards About Us
forimi.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

forimi.com

RELIABLE BEAUTY EQUIPMENT SUPPLIER-FORIMI

Page Load Speed

4.9 sec in total

First Response

283 ms

Resources Loaded

3.8 sec

Page Rendered

805 ms

forimi.com screenshot

About Website

Visit forimi.com now to see the best up-to-date FORIMI content for Singapore and also check out these interesting facts you probably never knew about forimi.com

Forimi was established since 2002 and located in Shunyi District, Beijing, China. We integrated R&D, production, sales and training services for a highly efficient and optimal manufacturing corporatio...

Visit forimi.com

Key Findings

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

Performance Metrics

forimi.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value17.0 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.241

52/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

forimi.com

283 ms

www.forimi.com

840 ms

common.css

29 ms

all.css

87 ms

kill-ie.css

84 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 58% of them (41 requests) were addressed to the original Forimi.com, 15% (11 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Cdn.globalso.com.

Page Optimization Overview & Recommendations

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

Content Size

4.2 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forimi.com main page is 4.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. Only a small number of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 36.1 kB

  • Original 44.2 kB
  • After minification 37.8 kB
  • After compression 8.0 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 6.4 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 36.1 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 194.4 kB

  • Original 3.4 MB
  • After minification 3.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. FORIMI images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 240.4 kB

  • Original 527.0 kB
  • After minification 527.0 kB
  • After compression 286.6 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 240.4 kB or 46% of the original size.

CSS Optimization

-39%

Potential reduce by 68.5 kB

  • Original 175.2 kB
  • After minification 159.7 kB
  • After compression 106.7 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. Forimi.com needs all CSS files to be minified and compressed as it can save up to 68.5 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (43%)

Requests Now

56

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forimi.com

forimi.com

283 ms

www.forimi.com

www.forimi.com

840 ms

common.css

common.css

29 ms

all.css

all.css

87 ms

kill-ie.css

kill-ie.css

84 ms

jquery.fullPage.css

jquery.fullPage.css

84 ms

layer.css

layer.css

86 ms

style.css

style.css

114 ms

style.min.css

style.min.css

94 ms

bsearch-styles.min.css

bsearch-styles.min.css

111 ms

pagenavi-css.css

pagenavi-css.css

111 ms

all.js

all.js

200 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

160 ms

layer.js

layer.js

161 ms

common.js

common.js

162 ms

css2

css2

28 ms

font_1949298_wk1ji6j33nk.css

font_1949298_wk1ji6j33nk.css

82 ms

gtm.js

gtm.js

103 ms

xhltrackingwithchat.js

xhltrackingwithchat.js

161 ms

fbevents.js

fbevents.js

54 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

55 ms

7KhNE4Oxz1Q

7KhNE4Oxz1Q

132 ms

xhlform_NEW.js

xhlform_NEW.js

130 ms

foot_whatsapp.png

foot_whatsapp.png

1976 ms

logo-1.png

logo-1.png

41 ms

h-ss.png

h-ss.png

41 ms

%E9%A9%AC%E6%9D%A5%E8%A5%BF%E4%BA%9A%E7%BA%BF%E4%B8%8A-1920x1053-%E6%8B%B7%E8%B4%9D-1.jpg

%E9%A9%AC%E6%9D%A5%E8%A5%BF%E4%BA%9A%E7%BA%BF%E4%B8%8A-1920x1053-%E6%8B%B7%E8%B4%9D-1.jpg

384 ms

%E9%A9%AC%E6%9D%A5%E8%A5%BF%E4%BA%9A%E7%BA%BF%E4%B8%8A-750x411-%E6%8B%B7%E8%B4%9D-1.jpg

%E9%A9%AC%E6%9D%A5%E8%A5%BF%E4%BA%9A%E7%BA%BF%E4%B8%8A-750x411-%E6%8B%B7%E8%B4%9D-1.jpg

116 ms

%E6%B3%A2%E5%85%B0%E7%BA%BF%E4%B8%8A-1920x1053-%E6%8B%B7%E8%B4%9D-1.jpg

%E6%B3%A2%E5%85%B0%E7%BA%BF%E4%B8%8A-1920x1053-%E6%8B%B7%E8%B4%9D-1.jpg

296 ms

%E6%B3%A2%E5%85%B0%E7%BA%BF%E4%B8%8A-750x411-%E6%8B%B7%E8%B4%9D-1.jpg

%E6%B3%A2%E5%85%B0%E7%BA%BF%E4%B8%8A-750x411-%E6%8B%B7%E8%B4%9D-1.jpg

116 ms

%E9%9D%A2%E7%A3%811920-10531.jpg

%E9%9D%A2%E7%A3%811920-10531.jpg

385 ms

%E9%9D%A2%E7%A3%81750-4111.jpg

%E9%9D%A2%E7%A3%81750-4111.jpg

130 ms

banner1.jpg

banner1.jpg

383 ms

banner1-1.jpg

banner1-1.jpg

296 ms

%E7%A3%81%E5%8A%9B%E7%98%A6%E5%AE%98%E7%BD%91%E7%94%A8-%E6%8B%B7%E8%B4%9D.jpg

%E7%A3%81%E5%8A%9B%E7%98%A6%E5%AE%98%E7%BD%91%E7%94%A8-%E6%8B%B7%E8%B4%9D.jpg

387 ms

%E8%B4%9F%E5%8E%8B%E5%BE%AE%E9%92%881920-1000-%E6%8B%B7%E8%B4%9D.jpg

%E8%B4%9F%E5%8E%8B%E5%BE%AE%E9%92%881920-1000-%E6%8B%B7%E8%B4%9D.jpg

386 ms

123.jpg

123.jpg

384 ms

123-1.jpg

123-1.jpg

388 ms

88o.jpg

88o.jpg

385 ms

ind-conbg.png

ind-conbg.png

387 ms

fb.png

fb.png

387 ms

in.png

in.png

388 ms

utube.png

utube.png

388 ms

Twitter.png

Twitter.png

389 ms

Instagram.png

Instagram.png

389 ms

f-add.png

f-add.png

390 ms

f-tel.png

f-tel.png

390 ms

f-mail.png

f-mail.png

390 ms

gotop.png

gotop.png

391 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrGFuW6O.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrGFuW6O.ttf

53 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrG3uW6O.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrG3uW6O.ttf

58 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrHbuW6O.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrHbuW6O.ttf

78 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEFuW6O.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEFuW6O.ttf

79 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrGFuG6O.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrGFuG6O.ttf

79 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrFbvm6O.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrFbvm6O.ttf

80 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrFivm6O.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrFivm6O.ttf

78 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEFvm6O.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEFvm6O.ttf

78 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEsvm6O.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEsvm6O.ttf

79 ms

font_1949298_wk1ji6j33nk.woff

font_1949298_wk1ji6j33nk.woff

478 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

1 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

24 ms

base.js

base.js

45 ms

ad_status.js

ad_status.js

151 ms

L24uOtqvNfFRO5TOxiIOVgM50wph5QKjT82e9pNVgC0.js

L24uOtqvNfFRO5TOxiIOVgM50wph5QKjT82e9pNVgC0.js

109 ms

embed.js

embed.js

39 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

24 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

24 ms

id

id

17 ms

Create

Create

73 ms

GenerateIT

GenerateIT

20 ms

Accessibility Review

forimi.com accessibility score

70

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

forimi.com 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

Page has valid source maps

SEO Factors

forimi.com SEO score

77

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 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 Forimi.com 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 Forimi.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

forimi.com

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