Tools & Wizards About Us
hammerandforge.net screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

hammerandforge.net

Hammer & Forge Artistic Architectural Iron Work. Kyle Walton. Edmonton

Page Load Speed

2.3 sec in total

First Response

161 ms

Resources Loaded

1.9 sec

Page Rendered

198 ms

hammerandforge.net screenshot

About Website

Click here to check amazing Hammer And Forge content. Otherwise, check out these important facts you probably never knew about hammerandforge.net

We create unique hand crafted Artistic Architectural Ironwork. Some of our work includes wrought iron railings, gates and addresses.

Visit hammerandforge.net

Key Findings

We analyzed Hammerandforge.net page load time and found that the first response time was 161 ms and then it took 2.1 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

hammerandforge.net performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.22

57/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

hammerandforge.net

161 ms

hammerandforge.net

556 ms

style.css

71 ms

colorbox.css

136 ms

style.css

246 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 81% of them (56 requests) were addressed to the original Hammerandforge.net, 10% (7 requests) were made to I0.wp.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (565 ms) belongs to the original domain Hammerandforge.net.

Page Optimization Overview & Recommendations

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

Content Size

696.2 kB

After Optimization

523.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hammerandforge.net main page is 696.2 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. 50% of websites need less resources to load. Javascripts take 304.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 64.7 kB

  • Original 80.1 kB
  • After minification 67.7 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 12.4 kB, which is 16% 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 64.7 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 27.5 kB

  • Original 248.9 kB
  • After minification 221.4 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, Hammer And Forge needs image optimization as it can save up to 27.5 kB or 11% 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 62.1 kB

  • Original 304.7 kB
  • After minification 304.2 kB
  • After compression 242.5 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 62.1 kB or 20% of the original size.

CSS Optimization

-29%

Potential reduce by 18.5 kB

  • Original 62.6 kB
  • After minification 62.6 kB
  • After compression 44.1 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. Hammerandforge.net needs all CSS files to be minified and compressed as it can save up to 18.5 kB or 29% of the original size.

Requests Breakdown

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

Requests Now

64

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hammerandforge.net

hammerandforge.net

161 ms

hammerandforge.net

hammerandforge.net

556 ms

style.css

style.css

71 ms

colorbox.css

colorbox.css

136 ms

style.css

style.css

246 ms

view.css

view.css

188 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

198 ms

wp-mediaelement.css

wp-mediaelement.css

199 ms

styles.css

styles.css

198 ms

fancybox.css

fancybox.css

201 ms

styles.min.css

styles.min.css

251 ms

woocommerce.css

woocommerce.css

264 ms

orange.css

orange.css

267 ms

hacks.css

hacks.css

268 ms

jquery.js

jquery.js

395 ms

jquery-migrate.js

jquery-migrate.js

308 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

310 ms

jquery.fancybox.js

jquery.fancybox.js

394 ms

tabs_slides.js

tabs_slides.js

330 ms

tabs_slides_opt_loader.js

tabs_slides_opt_loader.js

330 ms

jquery.min.js

jquery.min.js

34 ms

jquery.quicksand.js

jquery.quicksand.js

368 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

371 ms

hoverIntent.js

hoverIntent.js

444 ms

superfish.js

superfish.js

445 ms

supersubs.js

supersubs.js

446 ms

custom.js

custom.js

446 ms

twitter.js

twitter.js

470 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

471 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

483 ms

comment-reply.js

comment-reply.js

484 ms

image-cdn.js

image-cdn.js

506 ms

index.js

index.js

505 ms

index.js

index.js

524 ms

scripts.min.js

scripts.min.js

525 ms

jquery.blockUI.js

jquery.blockUI.js

526 ms

woocommerce.js

woocommerce.js

526 ms

jquery.cookie.js

jquery.cookie.js

565 ms

api.js

api.js

76 ms

e-202446.js

e-202446.js

23 ms

cart-fragments.js

cart-fragments.js

564 ms

jquery.placeholder.js

jquery.placeholder.js

522 ms

wp-polyfill.js

wp-polyfill.js

471 ms

index.js

index.js

419 ms

analytics.js

analytics.js

30 ms

collect

collect

39 ms

slider1a11.jpg

slider1a11.jpg

57 ms

topbar_bg.jpg

topbar_bg.jpg

141 ms

google1.png

google1.png

151 ms

facebook1.png

facebook1.png

151 ms

search_icon.jpg

search_icon.jpg

179 ms

cart_small.png

cart_small.png

180 ms

hammerandforge_footer.png

hammerandforge_footer.png

181 ms

hammerandforge.net

hammerandforge.net

416 ms

feat_img_shadow.png

feat_img_shadow.png

211 ms

dark_texture.jpg

dark_texture.jpg

274 ms

footer_logo.png

footer_logo.png

244 ms

hf_copy1.png

hf_copy1.png

246 ms

slider2.jpg

slider2.jpg

36 ms

img_2423-scaled.jpg

img_2423-scaled.jpg

117 ms

cec5330c-dee8-466b-b8bc-a74bf56f8bee.jpg

cec5330c-dee8-466b-b8bc-a74bf56f8bee.jpg

37 ms

DSC_0411-e1540400411159.jpg

DSC_0411-e1540400411159.jpg

35 ms

DSC_0427.jpg

DSC_0427.jpg

36 ms

DSC_0828.jpg

DSC_0828.jpg

38 ms

js

js

71 ms

muli-regular-webfont.woff

muli-regular-webfont.woff

220 ms

Quicksand_Bold-webfont.woff

Quicksand_Bold-webfont.woff

246 ms

bullets.png

bullets.png

121 ms

bg_direction_nav.png

bg_direction_nav.png

290 ms

Accessibility Review

hammerandforge.net accessibility score

58

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hammerandforge.net best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hammerandforge.net SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

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

hammerandforge.net

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