Tools & Wizards About Us
percom.org screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

percom.org

IEEE International Conference on Pervasive Computing and Communication – IEEE PerCom – the premier IEEE conference on pervasive computing

Page Load Speed

1.7 sec in total

First Response

145 ms

Resources Loaded

1.3 sec

Page Rendered

261 ms

percom.org screenshot

About Website

Click here to check amazing Per Com content for United States. Otherwise, check out these important facts you probably never knew about percom.org

Visit percom.org

Key Findings

We analyzed Percom.org page load time and found that the first response time was 145 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

percom.org performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

percom.org

145 ms

www.percom.org

385 ms

style.min.css

129 ms

mediaelementplayer-legacy.min.css

183 ms

wp-mediaelement.min.css

182 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 67% of them (16 requests) were addressed to the original Percom.org, 21% (5 requests) were made to I0.wp.com and 8% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (404 ms) belongs to the original domain Percom.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.2 kB (23%)

Content Size

456.3 kB

After Optimization

351.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Percom.org main page is 456.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. 25% of websites need less resources to load. Images take 192.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 49.8 kB

  • Original 64.8 kB
  • After minification 62.9 kB
  • After compression 15.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 49.8 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 192.1 kB
  • After minification 192.1 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. Per Com images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 21.4 kB

  • Original 91.1 kB
  • After minification 91.1 kB
  • After compression 69.7 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 21.4 kB or 24% of the original size.

CSS Optimization

-31%

Potential reduce by 34.0 kB

  • Original 108.4 kB
  • After minification 108.4 kB
  • After compression 74.4 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. Percom.org needs all CSS files to be minified and compressed as it can save up to 34.0 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (68%)

Requests Now

22

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

percom.org

percom.org

145 ms

www.percom.org

www.percom.org

385 ms

style.min.css

style.min.css

129 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

183 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

182 ms

utilities.css

utilities.css

198 ms

cookie-law-info-public.css

cookie-law-info-public.css

186 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

187 ms

style-index.css

style-index.css

191 ms

theme-bootstrap4.min.css

theme-bootstrap4.min.css

366 ms

utilities.js

utilities.js

246 ms

jquery.min.js

jquery.min.js

315 ms

jquery-migrate.min.js

jquery-migrate.min.js

251 ms

cookie-law-info-public.js

cookie-law-info-public.js

255 ms

sdk.js

sdk.js

17 ms

cookie-law-info-table.css

cookie-law-info-table.css

210 ms

theme-bootstrap4.min.js

theme-bootstrap4.min.js

404 ms

e-202431.js

e-202431.js

16 ms

PerCom25_Banner_R2.jpg

PerCom25_Banner_R2.jpg

86 ms

IEEE-CS_Logo.webp

IEEE-CS_Logo.webp

55 ms

TCPP-500x174-2.webp

TCPP-500x174-2.webp

74 ms

tccc_1-1.webp

tccc_1-1.webp

140 ms

Elsevier_cover-1.webp

Elsevier_cover-1.webp

74 ms

sdk.js

sdk.js

14 ms

Accessibility Review

percom.org accessibility score

96

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

Best Practices

percom.org 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

percom.org SEO score

87

Search Engine Optimization Advices

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 Percom.org 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 Percom.org 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

percom.org

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