Tools & Wizards About Us
sourceme.net screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

sourceme.net

Retail Display | Acrylic Fabrication | Digital Printing | Kiosk

Page Load Speed

8.7 sec in total

First Response

552 ms

Resources Loaded

7.7 sec

Page Rendered

531 ms

sourceme.net screenshot

About Website

Visit sourceme.net now to see the best up-to-date Sourceme content for India and also check out these interesting facts you probably never knew about sourceme.net

SourceMe is a multifaceted organization that develops and manufactures retail display solutions, BTL display, acrylic fabrication, digital printing, kiosk, etc

Visit sourceme.net

Key Findings

We analyzed Sourceme.net page load time and found that the first response time was 552 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

sourceme.net performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value19.0 s

0/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.2 s

1/100

10%

Network Requests Diagram

sourceme.net

552 ms

www.sourceme.net

1114 ms

js

68 ms

css

35 ms

icofont.min.css

464 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 87% of them (79 requests) were addressed to the original Sourceme.net, 7% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Sourceme.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.2 kB (4%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sourceme.net main page is 1.7 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. 65% of websites need less resources to load. Images take 849.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 47.6 kB

  • Original 54.5 kB
  • After minification 37.5 kB
  • After compression 6.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 17.0 kB, which is 31% 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 47.6 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 13.9 kB

  • Original 849.5 kB
  • After minification 835.6 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. Sourceme images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 7.0 kB

  • Original 698.3 kB
  • After minification 698.3 kB
  • After compression 691.3 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

-5%

Potential reduce by 4.6 kB

  • Original 91.4 kB
  • After minification 91.4 kB
  • After compression 86.8 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. Sourceme.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 47 (59%)

Requests Now

80

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sourceme.net

sourceme.net

552 ms

www.sourceme.net

www.sourceme.net

1114 ms

js

js

68 ms

css

css

35 ms

icofont.min.css

icofont.min.css

464 ms

linearicons.min.css

linearicons.min.css

470 ms

magnific-popup.min.css

magnific-popup.min.css

468 ms

animsition.min.css

animsition.min.css

472 ms

swiper.min.css

swiper.min.css

483 ms

bootstrap.min.css

bootstrap.min.css

734 ms

settings.css

settings.css

695 ms

layers.css

layers.css

696 ms

revolution.addon.panorama.css

revolution.addon.panorama.css

701 ms

theme.css

theme.css

942 ms

responsive.css

responsive.css

721 ms

dark.css

dark.css

925 ms

jquery.min.js

jquery.min.js

31 ms

logo.png

logo.png

922 ms

polyfill.min.js

polyfill.min.js

1167 ms

jquery.min.js

jquery.min.js

1207 ms

jquery.viewport.min.js

jquery.viewport.min.js

1047 ms

jQuerySimpleCounter.min.js

jQuerySimpleCounter.min.js

1151 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1155 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

1198 ms

animsition.min.js

animsition.min.js

1232 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

1606 ms

rellax.min.js

rellax.min.js

1386 ms

swiper.min.js

swiper.min.js

1635 ms

smoothscroll.js

smoothscroll.js

1413 ms

svg4everybody.legacy.min.js

svg4everybody.legacy.min.js

1449 ms

TweenMax.min.js

TweenMax.min.js

1706 ms

TimelineLite.min.js

TimelineLite.min.js

1619 ms

typed.min.js

typed.min.js

1649 ms

vivus.min.js

vivus.min.js

1690 ms

water.js

water.js

3021 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

2084 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1871 ms

three.min.js

three.min.js

2595 ms

revolution.addon.panorama.min.js

revolution.addon.panorama.min.js

1931 ms

revolution.addon.slicey.min.js

revolution.addon.slicey.min.js

1948 ms

revolution.extension.actions.min.js

revolution.extension.actions.min.js

2104 ms

js

js

49 ms

analytics.js

analytics.js

16 ms

collect

collect

29 ms

revolution.extension.carousel.min.js

revolution.extension.carousel.min.js

1716 ms

revolution.extension.kenburn.min.js

revolution.extension.kenburn.min.js

1730 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

1855 ms

revolution.extension.migration.min.js

revolution.extension.migration.min.js

1876 ms

revolution.extension.navigation.min.js

revolution.extension.navigation.min.js

1941 ms

revolution.extension.parallax.min.js

revolution.extension.parallax.min.js

1745 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

1856 ms

revolution.extension.video.min.js

revolution.extension.video.min.js

1879 ms

theme.js

theme.js

1942 ms

go-down.png

go-down.png

1947 ms

clientsource1.jpg

clientsource1.jpg

1863 ms

clientsource2.jpg

clientsource2.jpg

1887 ms

clientsource3.jpg

clientsource3.jpg

1788 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

15 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

25 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

50 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

59 ms

LYjYdG7kmE0gV69VVPPdFl06VN8XG4S11zY.ttf

LYjYdG7kmE0gV69VVPPdFl06VN8XG4S11zY.ttf

58 ms

LYjYdG7kmE0gV69VVPPdFl06VN9JG4S11zY.ttf

LYjYdG7kmE0gV69VVPPdFl06VN9JG4S11zY.ttf

59 ms

Linearicons.woff

Linearicons.woff

3292 ms

Icofont.woff

Icofont.woff

3938 ms

clientsource5.jpg

clientsource5.jpg

1859 ms

clientsource6.jpg

clientsource6.jpg

1889 ms

clientsource4.jpg

clientsource4.jpg

1885 ms

home-studio-video-imagefinal.jpg

home-studio-video-imagefinal.jpg

3621 ms

list_aester001.jpg

list_aester001.jpg

2017 ms

list_IMG_1607.jpg

list_IMG_1607.jpg

2353 ms

list_7e4998ae_207a_441c_b45d_a89183d14e0d.jpg

list_7e4998ae_207a_441c_b45d_a89183d14e0d.jpg

1892 ms

list_cooking_station007.jpg

list_cooking_station007.jpg

2031 ms

list_IMG_6148.jpg

list_IMG_6148.jpg

2162 ms

list_projects004.jpg

list_projects004.jpg

2542 ms

avatar_2.jpg

avatar_2.jpg

2329 ms

comment_avatar_2_1.jpg

comment_avatar_2_1.jpg

2361 ms

avatar_1_1.jpg

avatar_1_1.jpg

2512 ms

thumb_wall_to_wall_carpets_4.jpg

thumb_wall_to_wall_carpets_4.jpg

2518 ms

thumb_3d_signages.jpg

thumb_3d_signages.jpg

2519 ms

thumb_food_kiosks2.jpg

thumb_food_kiosks2.jpg

2506 ms

dot-dark.jpg

dot-dark.jpg

2534 ms

list_banner_retail_display_solution_display.jpg

list_banner_retail_display_solution_display.jpg

2497 ms

list_banner_livecooking_service.jpg

list_banner_livecooking_service.jpg

3192 ms

list_banner_acrylcwodmetal.jpg

list_banner_acrylcwodmetal.jpg

2958 ms

noimage-thumb.jpg

noimage-thumb.jpg

2993 ms

list_banner_carpets.jpg

list_banner_carpets.jpg

2743 ms

list_wall_to_wall_carpets.jpg

list_wall_to_wall_carpets.jpg

3655 ms

list_banner_signages.jpg

list_banner_signages.jpg

3125 ms

list_banner_largeprint.jpg

list_banner_largeprint.jpg

2893 ms

www.sourceme.net

www.sourceme.net

2964 ms

Accessibility Review

sourceme.net accessibility score

77

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

sourceme.net best practices score

67

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

Missing source maps for large first-party JavaScript

SEO Factors

sourceme.net SEO score

92

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

sourceme.net

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