Tools & Wizards About Us
pillid.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pillid.com

Pill Identifier and Identification Wizard - Pill ID

Page Load Speed

2.4 sec in total

First Response

136 ms

Resources Loaded

2.1 sec

Page Rendered

132 ms

pillid.com screenshot

About Website

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

Pill Identifier Quick Search Wizard. Free Pill Identification for the public and advanced drug identification wizard for professionals. Best Pill ID search on the internet.

Visit pillid.com

Key Findings

We analyzed Pillid.com page load time and found that the first response time was 136 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pillid.com performance score

0

Network Requests Diagram

pillid.com

136 ms

www.pillid.com

391 ms

front.css

142 ms

media.css

177 ms

chkpop.css

175 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 59% of them (42 requests) were addressed to the original Pillid.com, 8% (6 requests) were made to Googleads.g.doubleclick.net and 7% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Pillid.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 391.2 kB (63%)

Content Size

624.3 kB

After Optimization

233.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pillid.com main page is 624.3 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. 40% of websites need less resources to load. Javascripts take 522.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 27.9 kB

  • Original 37.0 kB
  • After minification 34.0 kB
  • After compression 9.1 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 27.9 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 28 B

  • Original 7.6 kB
  • After minification 7.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. Pill ID images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 317.1 kB

  • Original 522.5 kB
  • After minification 487.6 kB
  • After compression 205.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 317.1 kB or 61% of the original size.

CSS Optimization

-81%

Potential reduce by 46.2 kB

  • Original 57.2 kB
  • After minification 47.4 kB
  • After compression 11.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. Pillid.com needs all CSS files to be minified and compressed as it can save up to 46.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (70%)

Requests Now

64

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pill ID. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pillid.com

pillid.com

136 ms

www.pillid.com

www.pillid.com

391 ms

front.css

front.css

142 ms

media.css

media.css

177 ms

chkpop.css

chkpop.css

175 ms

validationEngine.css

validationEngine.css

176 ms

jquery.confirm.css

jquery.confirm.css

175 ms

jquery-1.10.2.js

jquery-1.10.2.js

340 ms

front.js

front.js

405 ms

jquery.tinyscrollbar.min.js

jquery.tinyscrollbar.min.js

365 ms

print.js

print.js

404 ms

jquery.validationEngine.js

jquery.validationEngine.js

531 ms

jquery.validationEngine-en.js

jquery.validationEngine-en.js

404 ms

jquery.confirm.js

jquery.confirm.js

590 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

590 ms

pace.min.js

pace.min.js

642 ms

adsbygoogle.js

adsbygoogle.js

57 ms

circle.player.css

circle.player.css

629 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

722 ms

jquery.transform2d.js

jquery.transform2d.js

698 ms

jquery.grab.js

jquery.grab.js

776 ms

mod.csstransforms.min.js

mod.csstransforms.min.js

765 ms

circle.player.js

circle.player.js

760 ms

ga.js

ga.js

54 ms

icon_update.png

icon_update.png

550 ms

latest-feeds.png

latest-feeds.png

551 ms

logo.png

logo.png

550 ms

username.png

username.png

627 ms

password.png

password.png

628 ms

e08e43b8cd9db43a4576699629bb5a9bb83ff96d.gif

e08e43b8cd9db43a4576699629bb5a9bb83ff96d.gif

632 ms

0370367cd928cb15933ea73b2b30150db87aac63.gif

0370367cd928cb15933ea73b2b30150db87aac63.gif

766 ms

home_print.png

home_print.png

929 ms

fb.png

fb.png

767 ms

pinterest.png

pinterest.png

844 ms

ggl_plus.png

ggl_plus.png

843 ms

twitter.png

twitter.png

814 ms

ajax-loader-orange.gif

ajax-loader-orange.gif

1036 ms

droidsans-webfont.woff

droidsans-webfont.woff

1025 ms

show_ads_impl.js

show_ads_impl.js

80 ms

zrt_lookup.html

zrt_lookup.html

40 ms

nav_icons.png

nav_icons.png

941 ms

logout.png

logout.png

985 ms

icon_api.png

icon_api.png

999 ms

__utm.gif

__utm.gif

13 ms

collect

collect

102 ms

cookie.js

cookie.js

106 ms

integrator.js

integrator.js

51 ms

ads

ads

395 ms

osd.js

osd.js

42 ms

ads

ads

661 ms

ads

ads

620 ms

controls.jpg

controls.jpg

684 ms

search_btn.png

search_btn.png

753 ms

footer_sep.png

footer_sep.png

769 ms

load_preloaded_resource.js

load_preloaded_resource.js

32 ms

abg_lite.js

abg_lite.js

34 ms

window_focus.js

window_focus.js

56 ms

osd_listener.js

osd_listener.js

22 ms

qs_click_protection.js

qs_click_protection.js

56 ms

2af0ddec604b54f0677af3c563b06c61.js

2af0ddec604b54f0677af3c563b06c61.js

28 ms

icon.png

icon.png

24 ms

s

s

24 ms

css

css

26 ms

7ACX1ll8pxmp-W5IFnwplmFbwq_vDvpxp5bFF4q7ftk.js

7ACX1ll8pxmp-W5IFnwplmFbwq_vDvpxp5bFF4q7ftk.js

3 ms

4UaGrENHsxJlGDuGo1OIlL3Owpg.woff

4UaGrENHsxJlGDuGo1OIlL3Owpg.woff

51 ms

4UabrENHsxJlGDuGo1OIlLU94YtzCwA.woff

4UabrENHsxJlGDuGo1OIlLU94YtzCwA.woff

57 ms

pixel

pixel

72 ms

css

css

32 ms

downsize_200k_v1

downsize_200k_v1

23 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

3 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

6 ms

SEO Factors

pillid.com SEO score

0

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

pillid.com

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