Tools & Wizards About Us
percipo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

percipo.com

Percipo: Video Analysis for Retail Analytics : Foot Traffic, Age Estimation and Gender Identification

Page Load Speed

1 sec in total

First Response

114 ms

Resources Loaded

576 ms

Page Rendered

313 ms

percipo.com screenshot

About Website

Welcome to percipo.com homepage info - get ready to check Percipo best content right away, or after learning these important things about percipo.com

Percipo develops applications and technology that can measure and accurately estimate various attributes of the human face including age, beauty and gender.

Visit percipo.com

Key Findings

We analyzed Percipo.com page load time and found that the first response time was 114 ms and then it took 889 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

percipo.com performance score

0

Network Requests Diagram

percipo.com

114 ms

www.percipo.com

122 ms

stylesheet.css

38 ms

preloadmenuimages.js

68 ms

ga.js

13 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 89% of them (16 requests) were addressed to the original Percipo.com, 11% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (258 ms) belongs to the original domain Percipo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.4 kB (10%)

Content Size

115.3 kB

After Optimization

103.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Percipo.com main page is 115.3 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. 15% of websites need less resources to load. Images take 87.2 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 5.3 kB

  • Original 7.3 kB
  • After minification 6.1 kB
  • After compression 2.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 1.2 kB, which is 17% 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 5.3 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 5.0 kB

  • Original 87.2 kB
  • After minification 82.2 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. Percipo images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 474 B

  • Original 18.0 kB
  • After minification 18.0 kB
  • After compression 17.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-26%

Potential reduce by 728 B

  • Original 2.9 kB
  • After minification 2.9 kB
  • After compression 2.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. Percipo.com needs all CSS files to be minified and compressed as it can save up to 728 B or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (31%)

Requests Now

16

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

percipo.com

percipo.com

114 ms

www.percipo.com

www.percipo.com

122 ms

stylesheet.css

stylesheet.css

38 ms

preloadmenuimages.js

preloadmenuimages.js

68 ms

ga.js

ga.js

13 ms

background.gif

background.gif

161 ms

shadow_left_bg.jpg

shadow_left_bg.jpg

157 ms

shadow_left.jpg

shadow_left.jpg

157 ms

logo_cyan.gif

logo_cyan.gif

157 ms

spacer_blend.jpg

spacer_blend.jpg

162 ms

fromimages.jpg

fromimages.jpg

258 ms

spacer.gif

spacer.gif

157 ms

corner_bottom_left.gif

corner_bottom_left.gif

157 ms

corner_bottom_right.gif

corner_bottom_right.gif

158 ms

shadow_right_bg.jpg

shadow_right_bg.jpg

159 ms

shadow_right.jpg

shadow_right.jpg

159 ms

shadow_bottom.jpg

shadow_bottom.jpg

159 ms

__utm.gif

__utm.gif

33 ms

SEO Factors

percipo.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Percipo.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 Percipo.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

percipo.com

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