Tools & Wizards About Us
amalgamweb.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

amalgamweb.com

Brendan Parker's Online Portfolio :: User Interaction, Web Development, Multimedia, Technical Writing

Page Load Speed

2.1 sec in total

First Response

228 ms

Resources Loaded

1.7 sec

Page Rendered

175 ms

amalgamweb.com screenshot

About Website

Visit amalgamweb.com now to see the best up-to-date Amalgam Web content and also check out these interesting facts you probably never knew about amalgamweb.com

I am Brendan Parker, a multimedia developer foom Rochester, NY with over 10 years experience. I am a User Interaction Designer, Front End Web Designer and Developer, Technical Writer, Professor, Educa...

Visit amalgamweb.com

Key Findings

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

Performance Metrics

amalgamweb.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.091

92/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

amalgamweb.com

228 ms

404

735 ms

general.css

63 ms

moreinfo.css

120 ms

amenu.css

121 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Amalgamweb.com, 86% (48 requests) were made to Bdparker.com and 7% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (735 ms) relates to the external source Bdparker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.4 kB (9%)

Content Size

713.6 kB

After Optimization

648.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 15.8 kB

  • Original 19.7 kB
  • After minification 17.0 kB
  • After compression 3.9 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 2.7 kB, which is 14% 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 15.8 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 35.2 kB

  • Original 608.5 kB
  • After minification 573.3 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. Amalgam Web images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 11.9 kB

  • Original 78.3 kB
  • After minification 78.3 kB
  • After compression 66.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 11.9 kB or 15% of the original size.

CSS Optimization

-35%

Potential reduce by 2.5 kB

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

Requests Breakdown

Number of requests can be reduced by 18 (42%)

Requests Now

43

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amalgamweb.com

amalgamweb.com

228 ms

404

404

735 ms

general.css

general.css

63 ms

moreinfo.css

moreinfo.css

120 ms

amenu.css

amenu.css

121 ms

lean-slider.css

lean-slider.css

119 ms

sample-styles.css

sample-styles.css

120 ms

easybox.min.css

easybox.min.css

120 ms

css

css

26 ms

css

css

46 ms

css2

css2

34 ms

css2

css2

51 ms

rotatingImages.js

rotatingImages.js

122 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

178 ms

dropdown.js

dropdown.js

178 ms

popup.js

popup.js

178 ms

fixposition.js

fixposition.js

179 ms

playsound.js

playsound.js

179 ms

expand.js

expand.js

181 ms

moreinfo.js

moreinfo.js

238 ms

moreinfoScript.js

moreinfoScript.js

238 ms

jquery.magnifier.js

jquery.magnifier.js

240 ms

jquery.min.js

jquery.min.js

353 ms

amenu.js

amenu.js

243 ms

modernizr-2.6.1.min.js

modernizr-2.6.1.min.js

241 ms

lean-slider.js

lean-slider.js

299 ms

distrib.min.js

distrib.min.js

299 ms

easybox.min.js

easybox.min.js

298 ms

handlers.min.js

handlers.min.js

301 ms

autoload.min.js

autoload.min.js

302 ms

panel_canvas_5.js

panel_canvas_5.js

358 ms

404

404

247 ms

404

404

187 ms

404

404

192 ms

404

404

187 ms

404

404

244 ms

404

404

244 ms

404

404

244 ms

404

404

190 ms

404

404

192 ms

404

404

194 ms

bkg_bottom.png

bkg_bottom.png

130 ms

triangles_bkg.jpg

triangles_bkg.jpg

289 ms

backpanel.png

backpanel.png

179 ms

bdptitle.png

bdptitle.png

129 ms

blackHeader.png

blackHeader.png

129 ms

panel_00.png

panel_00.png

76 ms

panel_01.png

panel_01.png

179 ms

panel_02.png

panel_02.png

291 ms

panel_03.png

panel_03.png

241 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

53 ms

ga.js

ga.js

9 ms

arrow_down.png

arrow_down.png

130 ms

arrows.png

arrows.png

179 ms

bullets.png

bullets.png

180 ms

__utm.gif

__utm.gif

21 ms

Accessibility Review

amalgamweb.com accessibility score

95

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

Links do not have a discernible name

Best Practices

amalgamweb.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

amalgamweb.com SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

amalgamweb.com

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