Tools & Wizards About Us
neocol.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

neocol.com

Neocol | Helping Subscription Businesses Scale | Salesforce Consulting

Page Load Speed

3.9 sec in total

First Response

81 ms

Resources Loaded

3.2 sec

Page Rendered

640 ms

neocol.com screenshot

About Website

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

Supercharge Your Subscription Business with Neocol - Helping Subscription Businesses Scale and Grow Through the Power of Salesforce

Visit neocol.com

Key Findings

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

Performance Metrics

neocol.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.577

12/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

neocol.com

81 ms

neocol.com

2511 ms

index.min.css

16 ms

magnific-popup.min.css

17 ms

core.min.css

30 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 49% of them (42 requests) were addressed to the original Neocol.com, 49% (42 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Neocol.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 358.3 kB (52%)

Content Size

692.8 kB

After Optimization

334.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Neocol.com main page is 692.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 307.3 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 273.1 kB

  • Original 307.3 kB
  • After minification 298.8 kB
  • After compression 34.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. 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 273.1 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 38.3 kB
  • After minification 38.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. Neocol images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 52.8 kB

  • Original 280.0 kB
  • After minification 280.0 kB
  • After compression 227.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 52.8 kB or 19% of the original size.

CSS Optimization

-48%

Potential reduce by 32.4 kB

  • Original 67.2 kB
  • After minification 67.1 kB
  • After compression 34.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. Neocol.com needs all CSS files to be minified and compressed as it can save up to 32.4 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (83%)

Requests Now

40

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

neocol.com

neocol.com

81 ms

neocol.com

neocol.com

2511 ms

index.min.css

index.min.css

16 ms

magnific-popup.min.css

magnific-popup.min.css

17 ms

core.min.css

core.min.css

30 ms

style.min.css

style.min.css

28 ms

style.min.css

style.min.css

21 ms

main.css

main.css

15 ms

main-media-query.css

main-media-query.css

29 ms

animations.css

animations.css

26 ms

jquery.min.js

jquery.min.js

28 ms

jquery-migrate.min.js

jquery-migrate.min.js

41 ms

popper-1.16.1.min.js

popper-1.16.1.min.js

45 ms

tippy-5.2.1.min.js

tippy-5.2.1.min.js

46 ms

js

js

282 ms

et-core-unified-1354.min.css

et-core-unified-1354.min.css

43 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

40 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

41 ms

slick.min.css

slick.min.css

82 ms

popup.min.js

popup.min.js

87 ms

morphext.min.js

morphext.min.js

87 ms

welcomebar-front.js

welcomebar-front.js

90 ms

detectmobilebrowser.js

detectmobilebrowser.js

87 ms

mystickymenu.min.js

mystickymenu.min.js

91 ms

magnific-popup.js

magnific-popup.js

94 ms

main.min.js

main.min.js

92 ms

dtq-default-vb.js

dtq-default-vb.js

92 ms

scripts.min.js

scripts.min.js

103 ms

jquery.fitvids.js

jquery.fitvids.js

102 ms

frontend-bundle.min.js

frontend-bundle.min.js

101 ms

main.js

main.js

101 ms

common.js

common.js

134 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

135 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

135 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

135 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

134 ms

slick.min.js

slick.min.js

133 ms

preloader.gif

preloader.gif

144 ms

icn-arrow2.webp

icn-arrow2.webp

143 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff

192 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

303 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

316 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

316 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

314 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

317 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

316 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

314 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

356 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

355 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

355 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

356 ms

LinkedIn.png

LinkedIn.png

57 ms

salesforce_appexchange-1.png

salesforce_appexchange-1.png

56 ms

neocol_logo_color4x.png

neocol_logo_color4x.png

57 ms

modules.woff

modules.woff

177 ms

-W_8XJnvUD7dzB2C2_8IZ2Mo.woff

-W_8XJnvUD7dzB2C2_8IZ2Mo.woff

223 ms

-W_8XJnvUD7dzB2C2_8IZ2Mr.ttf

-W_8XJnvUD7dzB2C2_8IZ2Mr.ttf

221 ms

-W_8XJnvUD7dzB2Cx_wIZ2Mo.woff

-W_8XJnvUD7dzB2Cx_wIZ2Mo.woff

231 ms

-W_8XJnvUD7dzB2Cx_wIZ2Mr.ttf

-W_8XJnvUD7dzB2Cx_wIZ2Mr.ttf

222 ms

-W_8XJnvUD7dzB2C4_0IZ2Mo.woff

-W_8XJnvUD7dzB2C4_0IZ2Mo.woff

232 ms

-W_8XJnvUD7dzB2C4_0IZ2Mr.ttf

-W_8XJnvUD7dzB2C4_0IZ2Mr.ttf

222 ms

-W_8XJnvUD7dzB2Cv_4IZ2Mo.woff

-W_8XJnvUD7dzB2Cv_4IZ2Mo.woff

222 ms

-W_8XJnvUD7dzB2Cv_4IZ2Mr.ttf

-W_8XJnvUD7dzB2Cv_4IZ2Mr.ttf

223 ms

-W_8XJnvUD7dzB2Ck_kIZ2Mo.woff

-W_8XJnvUD7dzB2Ck_kIZ2Mo.woff

223 ms

-W_8XJnvUD7dzB2Ck_kIZ2Mr.ttf

-W_8XJnvUD7dzB2Ck_kIZ2Mr.ttf

223 ms

-W__XJnvUD7dzB2Kbtob.woff

-W__XJnvUD7dzB2Kbtob.woff

223 ms

-W__XJnvUD7dzB2KbtoY.ttf

-W__XJnvUD7dzB2KbtoY.ttf

224 ms

-W_8XJnvUD7dzB2Cy_gIZ2Mo.woff

-W_8XJnvUD7dzB2Cy_gIZ2Mo.woff

224 ms

-W_8XJnvUD7dzB2Cy_gIZ2Mr.ttf

-W_8XJnvUD7dzB2Cy_gIZ2Mr.ttf

225 ms

-W_8XJnvUD7dzB2Cr_sIZ2Mo.woff

-W_8XJnvUD7dzB2Cr_sIZ2Mo.woff

291 ms

-W_8XJnvUD7dzB2Cr_sIZ2Mr.ttf

-W_8XJnvUD7dzB2Cr_sIZ2Mr.ttf

224 ms

-W_9XJnvUD7dzB2CA-oRTkA.woff

-W_9XJnvUD7dzB2CA-oRTkA.woff

291 ms

-W_9XJnvUD7dzB2CA-oRTkM.ttf

-W_9XJnvUD7dzB2CA-oRTkM.ttf

225 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWV4exg.woff

225 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWV4exQ.ttf

226 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff

225 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

227 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff

225 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

227 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff

78 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

57 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff

56 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

54 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff

113 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

112 ms

Accessibility Review

neocol.com accessibility score

79

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

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

neocol.com SEO score

83

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neocol.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Neocol.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

neocol.com

Open Graph data is detected on the main page of Neocol. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: