Tools & Wizards About Us
webelements.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

webelements.com

The periodic table of the elements by WebElements

Page Load Speed

3.9 sec in total

First Response

181 ms

Resources Loaded

3.4 sec

Page Rendered

294 ms

webelements.com screenshot

About Website

Click here to check amazing Web Elements content for United States. Otherwise, check out these important facts you probably never knew about webelements.com

Explore the chemical elements through this periodic table

Visit webelements.com

Key Findings

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

Performance Metrics

webelements.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value4,270 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.26

47/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

webelements.com

181 ms

www.webelements.com

520 ms

js

58 ms

pure-min.css

288 ms

grids-responsive-min.css

368 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 19% of them (13 requests) were addressed to the original Webelements.com, 14% (10 requests) were made to Pagead2.googlesyndication.com and 12% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (712 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.4 kB (20%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 47.8 kB

  • Original 59.0 kB
  • After minification 55.6 kB
  • After compression 11.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 47.8 kB or 81% of the original size.

Image Optimization

-13%

Potential reduce by 55.4 kB

  • Original 443.1 kB
  • After minification 387.7 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. Obviously, Web Elements needs image optimization as it can save up to 55.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 151.8 kB

  • Original 778.2 kB
  • After minification 778.2 kB
  • After compression 626.4 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 151.8 kB or 20% of the original size.

CSS Optimization

-5%

Potential reduce by 408 B

  • Original 8.0 kB
  • After minification 8.0 kB
  • After compression 7.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. Webelements.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (66%)

Requests Now

61

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webelements.com

webelements.com

181 ms

www.webelements.com

www.webelements.com

520 ms

js

js

58 ms

pure-min.css

pure-min.css

288 ms

grids-responsive-min.css

grids-responsive-min.css

368 ms

periodic-table.css

periodic-table.css

368 ms

adsbygoogle.js

adsbygoogle.js

122 ms

logo_60.png

logo_60.png

365 ms

cookieconsent_306.min.css

cookieconsent_306.min.css

280 ms

cookieconsent_306.min.js

cookieconsent_306.min.js

280 ms

js

js

72 ms

analytics.js

analytics.js

172 ms

collect

collect

19 ms

collect

collect

10 ms

webelements-A2-cartograms-2010_w460.jpg

webelements-A2-cartograms-2010_w460.jpg

217 ms

periodic_table_standard.png

periodic_table_standard.png

429 ms

periodic_table_spiral_336.png

periodic_table_spiral_336.png

271 ms

periodic_table_circle_336.png

periodic_table_circle_336.png

271 ms

periodic_table_full_janet_336.png

periodic_table_full_janet_336.png

274 ms

collect

collect

114 ms

show_ads_impl.js

show_ads_impl.js

306 ms

plusone.js

plusone.js

54 ms

ga-audiences

ga-audiences

96 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

zrt_lookup.html

zrt_lookup.html

49 ms

ads

ads

453 ms

ads

ads

712 ms

27c0e1a3519c9354d4bc0ec1b5da6b54.js

27c0e1a3519c9354d4bc0ec1b5da6b54.js

46 ms

3b0c1a1c8750041eb27603629860e89a.js

3b0c1a1c8750041eb27603629860e89a.js

51 ms

load_preloaded_resource.js

load_preloaded_resource.js

47 ms

cdf01d8369ba0e15ccbc9395c59a9391.js

cdf01d8369ba0e15ccbc9395c59a9391.js

65 ms

f11bfab4e3c942216447974439595ef6.js

f11bfab4e3c942216447974439595ef6.js

47 ms

abg_lite.js

abg_lite.js

90 ms

window_focus.js

window_focus.js

92 ms

qs_click_protection.js

qs_click_protection.js

93 ms

ufs_web_display.js

ufs_web_display.js

17 ms

bbcd6bf18c20baa1b2adeb195de9b551.js

bbcd6bf18c20baa1b2adeb195de9b551.js

83 ms

icon.png

icon.png

32 ms

s

s

10 ms

css

css

191 ms

reactive_library.js

reactive_library.js

213 ms

ca-pub-9334432533380510

ca-pub-9334432533380510

152 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyzAFyo4d4k.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyzAFyo4d4k.ttf

43 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyzAFyo4d4k.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyzAFyo4d4k.ttf

44 ms

sodar

sodar

104 ms

activeview

activeview

158 ms

ads

ads

494 ms

ads

ads

324 ms

ads

ads

304 ms

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

116 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

12 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

147 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

154 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

151 ms

sodar2.js

sodar2.js

166 ms

runner.html

runner.html

10 ms

aframe

aframe

22 ms

feg8rL66UTsTrrlS9w_iUH8JqR_kCfLFdi2W6wljJCU.js

feg8rL66UTsTrrlS9w_iUH8JqR_kCfLFdi2W6wljJCU.js

6 ms

cookie_push_onload.html

cookie_push_onload.html

120 ms

r.gif

r.gif

115 ms

169 ms

pixel

pixel

26 ms

22 ms

pixel

pixel

86 ms

pixel

pixel

85 ms

pixel

pixel

84 ms

85 ms

activeview

activeview

139 ms

pixel

pixel

31 ms

Accessibility Review

webelements.com accessibility score

93

Accessibility Issues

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

Form elements do not have associated labels

Best Practices

webelements.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

webelements.com SEO score

90

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

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

webelements.com

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