Tools & Wizards About Us
nearbuzz.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

nearbuzz.com

** NearBuzz **

Page Load Speed

11.3 sec in total

First Response

47 ms

Resources Loaded

10.6 sec

Page Rendered

679 ms

nearbuzz.com screenshot

About Website

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

Technology and Innovation with modern AI

Visit nearbuzz.com

Key Findings

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

Performance Metrics

nearbuzz.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value6.7 s

57/100

10%

Network Requests Diagram

nearbuzz.com

47 ms

www.nearbuzz.com

59 ms

bootstrap.min.css

1407 ms

nearbuzz.css

993 ms

slick.css

812 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 78% of them (67 requests) were addressed to the original Nearbuzz.com, 16% (14 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Stackpath.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Nearbuzz.com.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

965.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 43.9 kB

  • Original 49.9 kB
  • After minification 36.2 kB
  • After compression 6.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 13.7 kB, which is 27% 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 43.9 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 48.9 kB

  • Original 916.3 kB
  • After minification 867.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. Near Buzz images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 4.7 kB

  • Original 67.8 kB
  • After minification 67.2 kB
  • After compression 63.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 779 B

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

Requests Breakdown

Number of requests can be reduced by 11 (17%)

Requests Now

66

After Optimization

55

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nearbuzz.com

nearbuzz.com

47 ms

www.nearbuzz.com

www.nearbuzz.com

59 ms

bootstrap.min.css

bootstrap.min.css

1407 ms

nearbuzz.css

nearbuzz.css

993 ms

slick.css

slick.css

812 ms

font-awesome.min.css

font-awesome.min.css

36 ms

jquery.bxslider.css

jquery.bxslider.css

17 ms

nearbuzz-logo-light.svg

nearbuzz-logo-light.svg

798 ms

hero-dashboard.svg

hero-dashboard.svg

1040 ms

hero-main-signage.svg

hero-main-signage.svg

2392 ms

advertisers_cr1.png

advertisers_cr1.png

2205 ms

advertisers_cr2.svg

advertisers_cr2.svg

1595 ms

advertisers_cr3.svg

advertisers_cr3.svg

1970 ms

advertisers_cr4.svg

advertisers_cr4.svg

1823 ms

mediaowners_cr1.svg

mediaowners_cr1.svg

2408 ms

mediaowners_cr2.svg

mediaowners_cr2.svg

2608 ms

mediaowners_cr3.svg

mediaowners_cr3.svg

2616 ms

mediaowners_cr4.svg

mediaowners_cr4.svg

2964 ms

reactions_icon.svg

reactions_icon.svg

3004 ms

engagement_icon.svg

engagement_icon.svg

3230 ms

count_icon.svg

count_icon.svg

3189 ms

dentsu.jpg

dentsu.jpg

3403 ms

hdf.jpg

hdf.jpg

3434 ms

panasonic.jpg

panasonic.jpg

3761 ms

skoda.jpg

skoda.jpg

3805 ms

McDonalds.jpg

McDonalds.jpg

3970 ms

Swiggy.jpg

Swiggy.jpg

4052 ms

spensers.jpg

spensers.jpg

4376 ms

lakme.jpg

lakme.jpg

4242 ms

Cheesiaano.jpg

Cheesiaano.jpg

4730 ms

venus.jpg

venus.jpg

4617 ms

kairos.jpg

kairos.jpg

4769 ms

kiddos.jpg

kiddos.jpg

5023 ms

mangalya.jpg

mangalya.jpg

5235 ms

bigc.jpg

bigc.jpg

5370 ms

creamstone.jpg

creamstone.jpg

5402 ms

ovkay.jpg

ovkay.jpg

5521 ms

openface.jpg

openface.jpg

5554 ms

js

js

64 ms

jquery.min.js

jquery.min.js

6223 ms

bootstrap.min.js

bootstrap.min.js

6197 ms

slick.js

slick.js

4579 ms

scroll.js

scroll.js

5356 ms

css2

css2

1711 ms

css2

css2

1731 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

5406 ms

addefy.jpg

addefy.jpg

5291 ms

adstruck.jpg

adstruck.jpg

5123 ms

hynetic.jpg

hynetic.jpg

5360 ms

vserv.jpg

vserv.jpg

5180 ms

rlsmart.jpg

rlsmart.jpg

5245 ms

startupindia.jpg

startupindia.jpg

4910 ms

thub.jpg

thub.jpg

4779 ms

nvidia.jpg

nvidia.jpg

4916 ms

startupschool.jpg

startupschool.jpg

5146 ms

startupaccelerator.jpg

startupaccelerator.jpg

5183 ms

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

15 ms

pxiEyp8kv8JHgFVrJJnedHFHGPezSQ.woff

pxiEyp8kv8JHgFVrJJnedHFHGPezSQ.woff

33 ms

pxiByp8kv8JHgFVrLGT9Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLGT9Z1xlE92JQEk.woff

39 ms

pxiByp8kv8JHgFVrLGT9Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLGT9Z1JlE92JQEl8qw.woff

41 ms

pxiByp8kv8JHgFVrLDz8Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLDz8Z1xlE92JQEk.woff

40 ms

pxiByp8kv8JHgFVrLDz8Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLDz8Z1JlE92JQEl8qw.woff

39 ms

pxiByp8kv8JHgFVrLFj_Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLFj_Z1xlE92JQEk.woff

41 ms

pxiByp8kv8JHgFVrLFj_Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLFj_Z1JlE92JQEl8qw.woff

66 ms

pxiByp8kv8JHgFVrLEj6Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLEj6Z1xlE92JQEk.woff

39 ms

pxiByp8kv8JHgFVrLEj6Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLEj6Z1JlE92JQEl8qw.woff

41 ms

pxiByp8kv8JHgFVrLCz7Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLCz7Z1xlE92JQEk.woff

42 ms

pxiByp8kv8JHgFVrLCz7Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLCz7Z1JlE92JQEl8qw.woff

65 ms

pxiByp8kv8JHgFVrLBT5Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLBT5Z1xlE92JQEk.woff

64 ms

pxiByp8kv8JHgFVrLBT5Z1JlE92JQEl8qw.woff

pxiByp8kv8JHgFVrLBT5Z1JlE92JQEl8qw.woff

63 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

37 ms

aws.jpg

aws.jpg

4958 ms

avishkar.jpg

avishkar.jpg

4966 ms

otis.jpg

otis.jpg

4837 ms

blog%203.jpg

blog%203.jpg

5310 ms

blog%202.jpg

blog%202.jpg

5536 ms

skoda-casestudy.jpg

skoda-casestudy.jpg

5551 ms

nearbuzz-icon-footer.svg

nearbuzz-icon-footer.svg

4943 ms

hero-bg-AImesh.svg

hero-bg-AImesh.svg

5374 ms

bg-mesh-advertisers.svg

bg-mesh-advertisers.svg

5026 ms

bg-mesh-mediaowners.svg

bg-mesh-mediaowners.svg

5280 ms

bg-mesh-technology.svg

bg-mesh-technology.svg

6213 ms

bg-mesh-blogs.svg

bg-mesh-blogs.svg

5707 ms

bg-mesh-footer.svg

bg-mesh-footer.svg

5559 ms

bx_loader.gif

bx_loader.gif

3298 ms

McDonalds.jpg

McDonalds.jpg

3537 ms

Accessibility Review

nearbuzz.com accessibility score

77

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best Practices

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

High

Page has valid source maps

SEO Factors

nearbuzz.com SEO score

75

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

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nearbuzz.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Nearbuzz.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

nearbuzz.com

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