Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

build.mk

build.mk » Forum

Page Load Speed

3.6 sec in total

First Response

369 ms

Resources Loaded

2.8 sec

Page Rendered

379 ms

build.mk screenshot

About Website

Visit build.mk now to see the best up-to-date Build content for Macedonia and also check out these interesting facts you probably never knew about build.mk

Портал од областа на градежништвото, архитектурата, инфраструктурен и урбан развој.

Visit build.mk

Key Findings

We analyzed Build.mk page load time and found that the first response time was 369 ms and then it took 3.2 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

build.mk performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.21

59/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

build.mk

369 ms

www.build.mk

906 ms

style.css

291 ms

tabs.js

169 ms

prototype.js

540 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 78% of them (45 requests) were addressed to the original Build.mk, 12% (7 requests) were made to Cdn.marketkonekt.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Build.mk.

Page Optimization Overview & Recommendations

Page size can be reduced by 327.8 kB (21%)

Content Size

1.6 MB

After Optimization

1.3 MB

In fact, the total size of Build.mk main page is 1.6 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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 24.8 kB

  • Original 33.2 kB
  • After minification 32.2 kB
  • After compression 8.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 24.8 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 80.9 kB

  • Original 1.3 MB
  • After minification 1.2 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. Build images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 161.6 kB

  • Original 220.4 kB
  • After minification 162.7 kB
  • After compression 58.8 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 161.6 kB or 73% of the original size.

CSS Optimization

-82%

Potential reduce by 60.5 kB

  • Original 73.5 kB
  • After minification 68.7 kB
  • After compression 13.0 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. Build.mk needs all CSS files to be minified and compressed as it can save up to 60.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (25%)

Requests Now

56

After Optimization

42

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

Accessibility Review

build.mk accessibility score

62

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

build.mk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

build.mk SEO score

58

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    SR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Build.mk can be misinterpreted by Google and other search engines. Our service has detected that Serbian is used on the page, and it does not match the claimed English language. Our system also found out that Build.mk 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

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