Tools & Wizards About Us
idcomms.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

idcomms.com

ID Comms: Brands Deserve Better Media

Page Load Speed

3.4 sec in total

First Response

254 ms

Resources Loaded

2.1 sec

Page Rendered

1 sec

idcomms.com screenshot

About Website

Click here to check amazing ID Comms content. Otherwise, check out these important facts you probably never knew about idcomms.com

Evidence-based consulting for ambitious brands looking to accelerate their competitive advantage in media.

Visit idcomms.com

Key Findings

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

Performance Metrics

idcomms.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,450 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

idcomms.com

254 ms

www.idcomms.com

241 ms

pwr-social.min.css

36 ms

pwr-shape.min.css

40 ms

pwr-burger.min.css

45 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 93% of them (119 requests) were addressed to the original Idcomms.com, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Static.hsappstatic.net. The less responsive or slowest element that took the longest time to load (882 ms) belongs to the original domain Idcomms.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 575.5 kB (25%)

Content Size

2.3 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Idcomms.com main page is 2.3 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 410.4 kB

  • Original 481.5 kB
  • After minification 470.7 kB
  • After compression 71.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 410.4 kB or 85% of the original size.

Image Optimization

-9%

Potential reduce by 150.5 kB

  • Original 1.7 MB
  • After minification 1.5 MB

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. ID Comms images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 7.5 kB

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

CSS Optimization

-12%

Potential reduce by 7.1 kB

  • Original 57.7 kB
  • After minification 57.7 kB
  • After compression 50.6 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. Idcomms.com needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 111 (91%)

Requests Now

122

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ID Comms. 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 74 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

idcomms.com

idcomms.com

254 ms

www.idcomms.com

www.idcomms.com

241 ms

pwr-social.min.css

pwr-social.min.css

36 ms

pwr-shape.min.css

pwr-shape.min.css

40 ms

pwr-burger.min.css

pwr-burger.min.css

45 ms

pwr-link.min.css

pwr-link.min.css

65 ms

pwr-filter.min.css

pwr-filter.min.css

47 ms

pwr-post.min.css

pwr-post.min.css

48 ms

pwr-blog.min.css

pwr-blog.min.css

57 ms

pwr-post-header.min.css

pwr-post-header.min.css

58 ms

pwr-avatar.min.css

pwr-avatar.min.css

65 ms

pwr-author.min.css

pwr-author.min.css

70 ms

pwr-email.min.css

pwr-email.min.css

80 ms

pwr-password.min.css

pwr-password.min.css

76 ms

pwr-sec-maintenance.min.css

pwr-sec-maintenance.min.css

78 ms

pwr-sec-coming.min.css

pwr-sec-coming.min.css

85 ms

pwr-countdown.min.css

pwr-countdown.min.css

89 ms

pwr-prev.min.css

pwr-prev.min.css

93 ms

pwr-toc.min.css

pwr-toc.min.css

94 ms

pwr-pillar.min.css

pwr-pillar.min.css

99 ms

pwr-sticky.min.css

pwr-sticky.min.css

105 ms

pwr-accordion.min.css

pwr-accordion.min.css

108 ms

pwr-sec-accordion.min.css

pwr-sec-accordion.min.css

122 ms

pwr-sec-breadcrumbs.min.css

pwr-sec-breadcrumbs.min.css

123 ms

pwr-sec-clients.min.css

pwr-sec-clients.min.css

114 ms

pwr-value.min.css

pwr-value.min.css

119 ms

pwr-sec-values.min.css

pwr-sec-values.min.css

132 ms

pwr-sec-cta.min.css

pwr-sec-cta.min.css

198 ms

pwr-sec-form.min.css

pwr-sec-form.min.css

142 ms

pwr-sec-guide.min.css

pwr-sec-guide.min.css

141 ms

pwr-image.min.css

pwr-image.min.css

144 ms

pwr-sec-image.min.css

pwr-sec-image.min.css

164 ms

pwr-hotspot.min.css

pwr-hotspot.min.css

156 ms

pwr-sec-map.min.css

pwr-sec-map.min.css

160 ms

pwr-sec-split.min.css

pwr-sec-split.min.css

162 ms

pwr-sec-mockup.min.css

pwr-sec-mockup.min.css

164 ms

pwr-price.min.css

pwr-price.min.css

179 ms

js

js

84 ms

js

js

127 ms

embed.js

embed.js

39 ms

loader.js

loader.js

53 ms

pwr-sec-price.min.css

pwr-sec-price.min.css

177 ms

pwr-sec-posts.min.css

pwr-sec-posts.min.css

163 ms

pwr-rel.min.css

pwr-rel.min.css

158 ms

pwr-services.min.css

pwr-services.min.css

157 ms

pwr-sec-services.min.css

pwr-sec-services.min.css

169 ms

pwr-sub-services.min.css

pwr-sub-services.min.css

162 ms

pwr-simple.min.css

pwr-simple.min.css

176 ms

pwr-sub-simple.min.css

pwr-sub-simple.min.css

159 ms

pwr-sec-simple.min.css

pwr-sec-simple.min.css

164 ms

pwr-stat.min.css

pwr-stat.min.css

163 ms

pwr-sec-stats.min.css

pwr-sec-stats.min.css

162 ms

pwr-sub-stats.min.css

pwr-sub-stats.min.css

168 ms

pwr-step.min.css

pwr-step.min.css

158 ms

pwr-sec-steps.min.css

pwr-sec-steps.min.css

172 ms

pwr-sub-steps.min.css

pwr-sub-steps.min.css

169 ms

pwr-team.min.css

pwr-team.min.css

168 ms

pwr-sec-team.min.css

pwr-sec-team.min.css

167 ms

pwr-sub-team.min.css

pwr-sub-team.min.css

165 ms

pwr-testimonial.min.css

pwr-testimonial.min.css

170 ms

pwr-sec-testimonials.min.css

pwr-sec-testimonials.min.css

173 ms

pwr-sec-txt.min.css

pwr-sec-txt.min.css

171 ms

pwr-tabs.min.css

pwr-tabs.min.css

165 ms

pwr-timeline.min.css

pwr-timeline.min.css

163 ms

pwr-sec-timeline.min.css

pwr-sec-timeline.min.css

178 ms

pwr-video-box.min.css

pwr-video-box.min.css

174 ms

pwr-sec-video.min.css

pwr-sec-video.min.css

174 ms

pwr-sub-image.min.css

pwr-sub-image.min.css

160 ms

pwr-mini.min.css

pwr-mini.min.css

152 ms

pwr-slider-old.min.css

pwr-slider-old.min.css

162 ms

pwr-slider.min.css

pwr-slider.min.css

159 ms

pwr-tooltip.min.css

pwr-tooltip.min.css

191 ms

pwr-sec-schedule.min.css

pwr-sec-schedule.min.css

161 ms

pwr-memberships.min.css

pwr-memberships.min.css

164 ms

scroll-shadow.min.css

scroll-shadow.min.css

169 ms

scroll-shadow.css

scroll-shadow.css

151 ms

module_93451991655_main-hero-id.min.css

module_93451991655_main-hero-id.min.css

374 ms

module_93463744363_high-light-text.min.css

module_93463744363_high-light-text.min.css

412 ms

module_123442348110_footer-awards-logos.min.css

module_123442348110_footer-awards-logos.min.css

165 ms

advanced-content.min.css

advanced-content.min.css

183 ms

pwr.min.js

pwr.min.js

158 ms

pwr-accordion.min.js

pwr-accordion.min.js

166 ms

pwr-blog-listing.min.js

pwr-blog-listing.min.js

172 ms

pwr-blog-post.min.js

pwr-blog-post.min.js

164 ms

pwr-burger.min.js

pwr-burger.min.js

180 ms

pwr-countdown.min.js

pwr-countdown.min.js

183 ms

pwr-guide.min.js

pwr-guide.min.js

176 ms

pwr-heights.min.js

pwr-heights.min.js

182 ms

pwr-lightbox.min.js

pwr-lightbox.min.js

189 ms

pwr-masonry.min.js

pwr-masonry.min.js

192 ms

pwr-match-height.min.js

pwr-match-height.min.js

186 ms

pwr-parallax.min.js

pwr-parallax.min.js

180 ms

pwr-search-results.min.js

pwr-search-results.min.js

193 ms

pwr-search.min.js

pwr-search.min.js

198 ms

pwr-stat.min.js

pwr-stat.min.js

196 ms

pwr-sticky-sub-menu.min.js

pwr-sticky-sub-menu.min.js

194 ms

pwr-swiper.min.js

pwr-swiper.min.js

191 ms

pwr-tabs.min.js

pwr-tabs.min.js

251 ms

pwr-toc.min.js

pwr-toc.min.js

215 ms

child.min.js

child.min.js

195 ms

project.js

project.js

234 ms

project.js

project.js

212 ms

JQuery-3.5.1.min.js

JQuery-3.5.1.min.js

226 ms

pwr.jquery.min.js

pwr.jquery.min.js

228 ms

scroll-shadow.min.js

scroll-shadow.min.js

248 ms

Typewriter.min.js

Typewriter.min.js

458 ms

Isotope.min.js

Isotope.min.js

448 ms

Packery.min.js

Packery.min.js

453 ms

2395501.js

2395501.js

433 ms

index.js

index.js

432 ms

idcomms_web_logo.svg

idcomms_web_logo.svg

107 ms

169%20ratio%20(1280%20%C3%97%20720%20px)%20(8).png

169%20ratio%20(1280%20%C3%97%20720%20px)%20(8).png

337 ms

id-comms-brands-deserve-better-media-2.jpg

id-comms-brands-deserve-better-media-2.jpg

108 ms

id-comms-we-want-your-brand-to-win.jpg

id-comms-we-want-your-brand-to-win.jpg

449 ms

ID_Comms_2022_Certification_Badge.png

ID_Comms_2022_Certification_Badge.png

882 ms

BWP%20Women.png

BWP%20Women.png

112 ms

BWP%20Wellness.png

BWP%20Wellness.png

446 ms

campaign-logo.svg

campaign-logo.svg

178 ms

adexchanger-logo-vector.svg

adexchanger-logo-vector.svg

180 ms

500.woff

500.woff

83 ms

regular.woff

regular.woff

83 ms

300.woff

300.woff

175 ms

700.woff

700.woff

299 ms

web-interactives-embed.js

web-interactives-embed.js

190 ms

leadflows.js

leadflows.js

201 ms

banner.js

banner.js

173 ms

2395501.js

2395501.js

248 ms

fb.js

fb.js

189 ms

Accessibility Review

idcomms.com accessibility score

95

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

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

idcomms.com SEO score

93

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

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

idcomms.com

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