Tools & Wizards About Us
buildresponse.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

buildresponse.com

Email Marketing Sri Lanka

Page Load Speed

4.7 sec in total

First Response

296 ms

Resources Loaded

4.1 sec

Page Rendered

348 ms

buildresponse.com screenshot

About Website

Welcome to buildresponse.com homepage info - get ready to check Buildresponse best content for United Arab Emirates right away, or after learning these important things about buildresponse.com

We Provide Email Marketing Services in Sri Lanka. Promote your Business in Sri Lanka with Email Marketing

Visit buildresponse.com

Key Findings

We analyzed Buildresponse.com page load time and found that the first response time was 296 ms and then it took 4.5 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

buildresponse.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value11.7 s

18/100

10%

Network Requests Diagram

buildresponse.com

296 ms

www.buildresponse.com

467 ms

style.css

264 ms

jquery.realperson.css

183 ms

responsive.css

188 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 78% of them (82 requests) were addressed to the original Buildresponse.com, 9% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Buildresponse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 805.9 kB (44%)

Content Size

1.8 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Buildresponse.com main page is 1.8 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. Images take 864.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 62.5 kB

  • Original 74.5 kB
  • After minification 46.3 kB
  • After compression 12.0 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 28.2 kB, which is 38% 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 62.5 kB or 84% of the original size.

Image Optimization

-14%

Potential reduce by 120.6 kB

  • Original 864.4 kB
  • After minification 743.9 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, Buildresponse needs image optimization as it can save up to 120.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 499.8 kB

  • Original 746.4 kB
  • After minification 707.8 kB
  • After compression 246.6 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 499.8 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 123.0 kB

  • Original 142.3 kB
  • After minification 103.5 kB
  • After compression 19.3 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. Buildresponse.com needs all CSS files to be minified and compressed as it can save up to 123.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (35%)

Requests Now

92

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

buildresponse.com

buildresponse.com

296 ms

www.buildresponse.com

www.buildresponse.com

467 ms

style.css

style.css

264 ms

jquery.realperson.css

jquery.realperson.css

183 ms

responsive.css

responsive.css

188 ms

theme-color.css

theme-color.css

181 ms

prettyPhoto.css

prettyPhoto.css

189 ms

reveal.css

reveal.css

185 ms

css

css

29 ms

modernizr.custom.js

modernizr.custom.js

272 ms

api.js

api.js

34 ms

javascript.gp

javascript.gp

182 ms

jquery.js

jquery.js

359 ms

jquery.tabSlideOut.js

jquery.tabSlideOut.js

254 ms

jquery.reveal.js

jquery.reveal.js

236 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

255 ms

jquery.tools.min.js

jquery.tools.min.js

299 ms

jquery.ddsmoothmenu.js

jquery.ddsmoothmenu.js

300 ms

tinynav.min.js

tinynav.min.js

300 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

304 ms

slides.min.jquery.js

slides.min.jquery.js

300 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

370 ms

jquery.fitvids.js

jquery.fitvids.js

372 ms

jquery.quicksand.js

jquery.quicksand.js

370 ms

jflickrfeed.min.js

jflickrfeed.min.js

376 ms

jquery.tweet.js

jquery.tweet.js

372 ms

js

js

24 ms

jquery.gmap.min.js

jquery.gmap.min.js

439 ms

custom.js

custom.js

447 ms

recaptcha__en.js

recaptcha__en.js

77 ms

bg.png

bg.png

261 ms

loader.gif

loader.gif

2653 ms

logo.png

logo.png

246 ms

1.jpg

1.jpg

2634 ms

2.jpg

2.jpg

2636 ms

3.jpg

3.jpg

2635 ms

4.jpg

4.jpg

2637 ms

5.jpg

5.jpg

2638 ms

6.jpg

6.jpg

2641 ms

author_thumb.jpg

author_thumb.jpg

2639 ms

author_thumb2.jpg

author_thumb2.jpg

2638 ms

forbes.jpg

forbes.jpg

2640 ms

mc.jpg

mc.jpg

2645 ms

dominos.jpg

dominos.jpg

2646 ms

porsche.jpg

porsche.jpg

2646 ms

prestige.jpg

prestige.jpg

2648 ms

audi.jpg

audi.jpg

2647 ms

westford.jpg

westford.jpg

2649 ms

gulfedu.jpg

gulfedu.jpg

2650 ms

grandholidays.jpg

grandholidays.jpg

2650 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

58 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

58 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

59 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

59 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

59 ms

mahindra.jpg

mahindra.jpg

2646 ms

nib.jpg

nib.jpg

2632 ms

dc.js

dc.js

47 ms

rfc.jpg

rfc.jpg

2592 ms

like.php

like.php

103 ms

classic.jpg

classic.jpg

2588 ms

anc.jpg

anc.jpg

2590 ms

icbt.jpg

icbt.jpg

2588 ms

jetwingholiday.jpg

jetwingholiday.jpg

2587 ms

sosa.woff

sosa.woff

2578 ms

__utm.gif

__utm.gif

19 ms

ozo.jpg

ozo.jpg

2521 ms

aod.jpg

aod.jpg

2521 ms

bms.jpg

bms.jpg

2521 ms

mercantile.jpg

mercantile.jpg

2520 ms

carmudi.jpg

carmudi.jpg

2521 ms

mclaren.jpg

mclaren.jpg

2509 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

29 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

16 ms

common.js

common.js

33 ms

util.js

util.js

45 ms

geocoder.js

geocoder.js

45 ms

jetwinghotels.jpg

jetwinghotels.jpg

2450 ms

supersavings.jpg

supersavings.jpg

2420 ms

nav_arrow_active.png

nav_arrow_active.png

2420 ms

custom_blocks_bg.png

custom_blocks_bg.png

2398 ms

widget_v2.134.js

widget_v2.134.js

15 ms

heading_bg.png

heading_bg.png

97 ms

bg_dark.png

bg_dark.png

77 ms

image_border_footer.png

image_border_footer.png

155 ms

goto_arrow_footer.png

goto_arrow_footer.png

93 ms

map_pin.png

map_pin.png

83 ms

telephone.png

telephone.png

82 ms

skype.png

skype.png

148 ms

list_item_star.png

list_item_star.png

187 ms

sprite_social.png

sprite_social.png

157 ms

modal-gloss.png

modal-gloss.png

253 ms

block_corner.png

block_corner.png

155 ms

subs.png

subs.png

268 ms

slider_arrow_prev.png

slider_arrow_prev.png

94 ms

slider_arrow_next.png

slider_arrow_next.png

82 ms

quote_small.png

quote_small.png

93 ms

quote_small_op.png

quote_small_op.png

156 ms

bubble_arrow.png

bubble_arrow.png

109 ms

author_thumb_shadow.png

author_thumb_shadow.png

79 ms

testimonials_nav.png

testimonials_nav.png

155 ms

03aPdn7fFF3H6ngCgAlQzC3USBnSvpkopQaUR-2r7iU.ttf

03aPdn7fFF3H6ngCgAlQzC3USBnSvpkopQaUR-2r7iU.ttf

7 ms

EgBlzoNBIHxNPCMwXaAhYPesZW2xOQ-xsNqO47m55DA.ttf

EgBlzoNBIHxNPCMwXaAhYPesZW2xOQ-xsNqO47m55DA.ttf

7 ms

QABk9IxT-LFTJ_dQzv7xpJ0EAVxt0G0biEntp43Qt6E.ttf

QABk9IxT-LFTJ_dQzv7xpJ0EAVxt0G0biEntp43Qt6E.ttf

11 ms

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

6 ms

Accessibility Review

buildresponse.com accessibility score

75

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

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

buildresponse.com 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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

buildresponse.com SEO score

82

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

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

buildresponse.com

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