Tools & Wizards About Us

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

eetimes.com

EE Times - Connecting The Global Electronics Industry

Page Load Speed

123.9 sec in total

First Response

202 ms

Resources Loaded

100.5 sec

Page Rendered

23.1 sec

About Website

Click here to check amazing EE Times content for India. Otherwise, check out these important facts you probably never knew about eetimes.com

EE Times offers reliable electronics news, electrical engineering resources, podcasts, and industry events from Award-winning journalists. Visit to learn more.

Visit eetimes.com

Key Findings

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

Performance Metrics

eetimes.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value3,790 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

eetimes.com

202 ms

www.eetimes.com

663 ms

ubm-global-footer.css

514 ms

eetimes.css

515 ms

complete.js

515 ms

Our browser made a total of 239 requests to load all elements on the main page. We found that 3% of them (6 requests) were addressed to the original Eetimes.com, 33% (80 requests) were made to M.eet.com and 6% (15 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (11.4 sec) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.2 MB (32%)

Content Size

10.0 MB

After Optimization

6.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eetimes.com main page is 10.0 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. Only a small number of websites need less resources to load. Images take 6.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 246.4 kB

  • Original 298.8 kB
  • After minification 282.5 kB
  • After compression 52.4 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 246.4 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 369.3 kB

  • Original 6.1 MB
  • After minification 5.8 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. EE Times images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 2.0 MB

  • Original 2.9 MB
  • After minification 2.8 MB
  • After compression 908.2 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 2.0 MB or 69% of the original size.

CSS Optimization

-80%

Potential reduce by 565.9 kB

  • Original 711.6 kB
  • After minification 682.9 kB
  • After compression 145.7 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. Eetimes.com needs all CSS files to be minified and compressed as it can save up to 565.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 140 (63%)

Requests Now

221

After Optimization

81

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

eetimes.com accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

eetimes.com SEO score

86

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

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

    N/A

  • Encoding

    ISO-8859-1

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

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