Tools & Wizards About Us
flaticons.net screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

flaticons.net

Royalty Free Flaticons - Flaticons.net

Page Load Speed

1.9 sec in total

First Response

420 ms

Resources Loaded

1.3 sec

Page Rendered

227 ms

flaticons.net screenshot

About Website

Welcome to flaticons.net homepage info - get ready to check Flaticons best content for China right away, or after learning these important things about flaticons.net

Flaticon maker. ✓ Over 8,000 royalty free flaticons. ✓ Customize within seconds. ✓

Visit flaticons.net

Key Findings

We analyzed Flaticons.net page load time and found that the first response time was 420 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

flaticons.net performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value6,350 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

flaticons.net

420 ms

bootstrap.css

40 ms

flat-ui.css

23 ms

master.css

12 ms

font-awesome.css

6 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 48% of them (65 requests) were addressed to the original Flaticons.net, 7% (10 requests) were made to Fonts.gstatic.com and 5% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (626 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.3 kB (54%)

Content Size

823.1 kB

After Optimization

375.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flaticons.net main page is 823.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 304.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 23.2 kB

  • Original 29.2 kB
  • After minification 29.2 kB
  • After compression 6.1 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 23.2 kB or 79% of the original size.

Image Optimization

-35%

Potential reduce by 105.7 kB

  • Original 304.7 kB
  • After minification 199.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, Flaticons needs image optimization as it can save up to 105.7 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-43%

Potential reduce by 95.1 kB

  • Original 222.1 kB
  • After minification 208.1 kB
  • After compression 127.0 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 95.1 kB or 43% of the original size.

CSS Optimization

-84%

Potential reduce by 223.4 kB

  • Original 267.1 kB
  • After minification 258.3 kB
  • After compression 43.8 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. Flaticons.net needs all CSS files to be minified and compressed as it can save up to 223.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (39%)

Requests Now

122

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flaticons.net

flaticons.net

420 ms

bootstrap.css

bootstrap.css

40 ms

flat-ui.css

flat-ui.css

23 ms

master.css

master.css

12 ms

font-awesome.css

font-awesome.css

6 ms

adsbygoogle.js

adsbygoogle.js

14 ms

css

css

32 ms

reset.css

reset.css

5 ms

global.css

global.css

6 ms

structure.css

structure.css

24 ms

formatting.css

formatting.css

24 ms

scrollbars.css

scrollbars.css

24 ms

css

css

23 ms

sdk.js

sdk.js

321 ms

analytics.js

analytics.js

40 ms

head-pattern.png

head-pattern.png

40 ms

logo.png

logo.png

34 ms

ca-pub-7625330445598969.js

ca-pub-7625330445598969.js

108 ms

zrt_lookup.html

zrt_lookup.html

106 ms

show_ads_impl.js

show_ads_impl.js

67 ms

Car.png

Car.png

37 ms

Painter.png

Painter.png

36 ms

Fish.png

Fish.png

36 ms

Documents.png

Documents.png

35 ms

Home.png

Home.png

36 ms

Jelly-Fish.png

Jelly-Fish.png

93 ms

Seahorse.png

Seahorse.png

83 ms

Dolphin.png

Dolphin.png

76 ms

Message-Mail.png

Message-Mail.png

76 ms

Password-Text-01.png

Password-Text-01.png

83 ms

Text-Normal.png

Text-Normal.png

85 ms

User-Profile.png

User-Profile.png

83 ms

Surfing.png

Surfing.png

251 ms

Ship-02.png

Ship-02.png

83 ms

CPU-01.png

CPU-01.png

84 ms

Office-01.png

Office-01.png

85 ms

Sailor-Wheel.png

Sailor-Wheel.png

85 ms

Sailor-Boat-02.png

Sailor-Boat-02.png

86 ms

Sailor-Boat-01.png

Sailor-Boat-01.png

89 ms

Boat.png

Boat.png

87 ms

Anchor-02.png

Anchor-02.png

89 ms

Editor.png

Editor.png

90 ms

Anchor-01.png

Anchor-01.png

91 ms

Facebook.png

Facebook.png

91 ms

Paging.png

Paging.png

92 ms

Magnifying-Glass.png

Magnifying-Glass.png

93 ms

Twitter.png

Twitter.png

93 ms

Search.png

Search.png

91 ms

Submit-01.png

Submit-01.png

94 ms

Crane.png

Crane.png

93 ms

Garbage-Open.png

Garbage-Open.png

94 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

81 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

83 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

84 ms

4cKlrioa77J2iqTqBgkRWg.ttf

4cKlrioa77J2iqTqBgkRWg.ttf

86 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

87 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

87 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

85 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

86 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

87 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

68 ms

collect

collect

60 ms

ads

ads

179 ms

osd.js

osd.js

68 ms

widgets.js

widgets.js

98 ms

plusone.js

plusone.js

85 ms

Recycle-Bin.png

Recycle-Bin.png

40 ms

Note-Memo.png

Note-Memo.png

40 ms

Edit.png

Edit.png

40 ms

Phone.png

Phone.png

39 ms

Shape-Star2.png

Shape-Star2.png

40 ms

Arrowhead-Left-01.png

Arrowhead-Left-01.png

44 ms

Arrowhead-Right-01.png

Arrowhead-Right-01.png

42 ms

YouTube1.png

YouTube1.png

43 ms

Volume-Mute.png

Volume-Mute.png

42 ms

Gear.png

Gear.png

41 ms

Monitor.png

Monitor.png

72 ms

Calculator.png

Calculator.png

216 ms

Certificate.png

Certificate.png

72 ms

Check.png

Check.png

72 ms

Tie-02.png

Tie-02.png

70 ms

Maps.png

Maps.png

91 ms

Industry.png

Industry.png

77 ms

Attachments-Remove.png

Attachments-Remove.png

71 ms

Thumbs-Up.png

Thumbs-Up.png

77 ms

Bomb.png

Bomb.png

90 ms

Joystick.png

Joystick.png

105 ms

Data-Settings.png

Data-Settings.png

105 ms

Octopus.png

Octopus.png

89 ms

ads

ads

277 ms

ads

ads

224 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

24 ms

like.php

like.php

112 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

47 ms

fastbutton

fastbutton

101 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

200 ms

m_js_controller.js

m_js_controller.js

75 ms

abg.js

abg.js

90 ms

postmessageRelay

postmessageRelay

135 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

38 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

37 ms

55 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

561 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

626 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

155 ms

xd_arbiter.php

xd_arbiter.php

288 ms

xd_arbiter.php

xd_arbiter.php

512 ms

favicon

favicon

97 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

107 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

29 ms

s

s

53 ms

x_button_blue2.png

x_button_blue2.png

48 ms

favicon

favicon

232 ms

api.js

api.js

76 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

110 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

120 ms

google

google

420 ms

bsredirect5.js

bsredirect5.js

112 ms

ca

ca

196 ms

tweet_button.6a78875565a912489e9aef879c881358.en.html

tweet_button.6a78875565a912489e9aef879c881358.en.html

63 ms

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

49 ms

bst2tv3.html

bst2tv3.html

98 ms

verifyc.js

verifyc.js

55 ms

jot

jot

99 ms

clk

clk

64 ms

wt12578_300x250.gif

wt12578_300x250.gif

41 ms

lidar.js

lidar.js

11 ms

dvtp_src.js

dvtp_src.js

41 ms

sbhK2lTE.js

sbhK2lTE.js

10 ms

cTrvNaRi.html

cTrvNaRi.html

22 ms

dvtp_src_internal25.js

dvtp_src_internal25.js

11 ms

t2tv7.html

t2tv7.html

58 ms

visit.js

visit.js

57 ms

avs5634.js

avs5634.js

4 ms

event.gif

event.gif

46 ms

Accessibility Review

flaticons.net accessibility score

47

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

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

flaticons.net 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

flaticons.net 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

    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 Flaticons.net 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 Flaticons.net 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

flaticons.net

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