Tools & Wizards About Us
eg.pico.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

eg.pico.com

Global Brand Activation Agency | Experience-led, Digital-first | Pico

Page Load Speed

7.2 sec in total

First Response

528 ms

Resources Loaded

5.8 sec

Page Rendered

837 ms

eg.pico.com screenshot

About Website

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

The Pico Group is a world-wide network of agencies that merge experiential, communications and technology talent to create powerful and engaging experiences that activate brands.

Visit eg.pico.com

Key Findings

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

Performance Metrics

eg.pico.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value22.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,240 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.333

34/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

eg.pico.com

528 ms

1320 ms

gtm.js

151 ms

pico-article.css

315 ms

content.css

312 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Eg.pico.com, 72% (54 requests) were made to Picowebcdn.pico.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Hm.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 822.1 kB (57%)

Content Size

1.4 MB

After Optimization

623.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Eg.pico.com main page is 1.4 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. 70% of websites need less resources to load. Javascripts take 747.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 54.4 kB

  • Original 71.4 kB
  • After minification 68.9 kB
  • After compression 17.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. 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 54.4 kB or 76% of the original size.

JavaScript Optimization

-42%

Potential reduce by 316.6 kB

  • Original 747.2 kB
  • After minification 731.8 kB
  • After compression 430.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 316.6 kB or 42% of the original size.

CSS Optimization

-72%

Potential reduce by 451.1 kB

  • Original 627.2 kB
  • After minification 543.6 kB
  • After compression 176.1 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. Eg.pico.com needs all CSS files to be minified and compressed as it can save up to 451.1 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (87%)

Requests Now

71

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eg.pico.com

eg.pico.com

528 ms

1320 ms

gtm.js

gtm.js

151 ms

pico-article.css

pico-article.css

315 ms

content.css

content.css

312 ms

js-offcanvas.css

js-offcanvas.css

312 ms

css

css

299 ms

template.css

template.css

375 ms

9.css

9.css

462 ms

custom.css

custom.css

546 ms

pico-form.css

pico-form.css

565 ms

request-for-proposal.css

request-for-proposal.css

906 ms

cookie.css

cookie.css

563 ms

responsive.css

responsive.css

902 ms

driving-change.css

driving-change.css

927 ms

we-are-global.css

we-are-global.css

1012 ms

total-brand-activation.css

total-brand-activation.css

1013 ms

we-are-digital.css

we-are-digital.css

1028 ms

template.css

template.css

1027 ms

reset.inline.min.css

reset.inline.min.css

1012 ms

site.inline.min.css

site.inline.min.css

1012 ms

semantic.min.css

semantic.min.css

1081 ms

text.css

text.css

1030 ms

fixes.semantic.css

fixes.semantic.css

1028 ms

wk-styles-c74c9444.css

wk-styles-c74c9444.css

1029 ms

jquery.min.js

jquery.min.js

1047 ms

bootstrap.bundle.js

bootstrap.bundle.js

1046 ms

jquery-migrate.min.js

jquery-migrate.min.js

1236 ms

js-offcanvas.pkgd.js

js-offcanvas.pkgd.js

1241 ms

bodyScrollLock.min.js

bodyScrollLock.min.js

1239 ms

offcanvas.js

offcanvas.js

1240 ms

base.js

base.js

1252 ms

jquery-noconflict.js

jquery-noconflict.js

1287 ms

cookie_script.js

cookie_script.js

1287 ms

semantic.min.js

semantic.min.js

1290 ms

g2.js

g2.js

1255 ms

g2.boot.js

g2.boot.js

1256 ms

g2.forms.js

g2.forms.js

1254 ms

g2.actions.js

g2.actions.js

1341 ms

conversion_async.js

conversion_async.js

677 ms

analytics.js

analytics.js

743 ms

insight.min.js

insight.min.js

734 ms

js

js

283 ms

fzo8nd5pqm.jsonp

fzo8nd5pqm.jsonp

768 ms

E-v1.js

E-v1.js

1156 ms

style.css

style.css

1090 ms

fontello.css

fontello.css

1088 ms

featherlight.min.css

featherlight.min.css

1087 ms

uikit2-0a76df6c.js

uikit2-0a76df6c.js

952 ms

wk-scripts-3df5abbf.js

wk-scripts-3df5abbf.js

956 ms

core.js

core.js

908 ms

TweenMax.min.js

TweenMax.min.js

890 ms

ScrollMagic.min.js

ScrollMagic.min.js

888 ms

collect

collect

411 ms

debug.addIndicators.min.js

debug.addIndicators.min.js

548 ms

animation.gsap.min.js

animation.gsap.min.js

533 ms

jarallax.min.js

jarallax.min.js

522 ms

434 ms

jarallax-video.min.js

jarallax-video.min.js

482 ms

featherlight.min.js

featherlight.min.js

491 ms

lazyload.min.js

lazyload.min.js

477 ms

pagination.min.js

pagination.min.js

469 ms

global.js

global.js

468 ms

collect

collect

184 ms

collect

collect

231 ms

179 ms

ga-audiences

ga-audiences

127 ms

hm.js

hm.js

1684 ms

pico_logo_white.svg

pico_logo_white.svg

71 ms

fontello.woff

fontello.woff

90 ms

fbevents.js

fbevents.js

101 ms

369d0e000c411c1fa16a526aa.js

369d0e000c411c1fa16a526aa.js

585 ms

474980056617752

474980056617752

413 ms

Socicon.ttf

Socicon.ttf

379 ms

21 ms

Accessibility Review

eg.pico.com accessibility score

100

Accessibility Issues

Best Practices

eg.pico.com 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

eg.pico.com SEO score

92

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

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

    EN

  • Encoding

    UTF-8

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

eg.pico.com

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