Tools & Wizards About Us
pert.me screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pert.me

Pert - Best Smart Home Automation Solutions in Hyderabad

Page Load Speed

2.5 sec in total

First Response

39 ms

Resources Loaded

1.1 sec

Page Rendered

1.3 sec

pert.me screenshot

About Website

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

Best smart home automation solutions in Hyderabad. Control lights, fans, curtains, appliances, and security systems from anywhere. Upgrade your home easily today.

Visit pert.me

Key Findings

We analyzed Pert.me page load time and found that the first response time was 39 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

pert.me performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value2,510 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

pert.me

39 ms

www.pert.me

234 ms

css2

62 ms

js

305 ms

style.min.css

13 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 70% of them (84 requests) were addressed to the original Pert.me, 9% (11 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (373 ms) belongs to the original domain Pert.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 283.7 kB (5%)

Content Size

5.6 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pert.me main page is 5.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. Only a small number of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 127.9 kB

  • Original 148.1 kB
  • After minification 87.5 kB
  • After compression 20.2 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 60.6 kB, which is 41% 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 127.9 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 145.1 kB

  • Original 5.0 MB
  • After minification 4.9 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. Pert images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 9.5 kB

  • Original 401.7 kB
  • After minification 401.7 kB
  • After compression 392.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

-2%

Potential reduce by 1.2 kB

  • Original 50.5 kB
  • After minification 50.4 kB
  • After compression 49.2 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. Pert.me has all CSS files already compressed.

Requests Breakdown

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

Requests Now

103

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pert.me

pert.me

39 ms

www.pert.me

www.pert.me

234 ms

css2

css2

62 ms

js

js

305 ms

style.min.css

style.min.css

13 ms

styles.css

styles.css

43 ms

frontend.css

frontend.css

47 ms

jquery-ui.css

jquery-ui.css

55 ms

wpcf7-redirect-frontend.min.css

wpcf7-redirect-frontend.min.css

42 ms

ivory-search.min.css

ivory-search.min.css

46 ms

swiper-bundle.min.css

swiper-bundle.min.css

58 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

48 ms

main.css

main.css

52 ms

addtoany.min.css

addtoany.min.css

51 ms

frontend-gtag.js

frontend-gtag.js

51 ms

jquery.min.js

jquery.min.js

77 ms

jquery-migrate.min.js

jquery-migrate.min.js

51 ms

page.js

page.js

142 ms

addtoany.min.js

addtoany.min.js

53 ms

ivory-ajax-search.min.css

ivory-ajax-search.min.css

53 ms

accordion.js

accordion.js

52 ms

index.js

index.js

53 ms

index.js

index.js

125 ms

heatmap.js

heatmap.js

126 ms

utils.js

utils.js

127 ms

drawing.js

drawing.js

130 ms

events.js

events.js

129 ms

frontend.js

frontend.js

134 ms

core.min.js

core.min.js

139 ms

mouse.min.js

mouse.min.js

130 ms

resizable.min.js

resizable.min.js

132 ms

draggable.min.js

draggable.min.js

132 ms

controlgroup.min.js

controlgroup.min.js

131 ms

checkboxradio.min.js

checkboxradio.min.js

132 ms

button.min.js

button.min.js

134 ms

dialog.min.js

dialog.min.js

136 ms

wpcf7r-fe.js

wpcf7r-fe.js

134 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

129 ms

swiper-bundle.min.js

swiper-bundle.min.js

156 ms

gsap.min.js

gsap.min.js

158 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

171 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

249 ms

jquery-ui.min.js

jquery-ui.min.js

252 ms

SplitText3.min.js

SplitText3.min.js

136 ms

common.js

common.js

153 ms

home.js

home.js

134 ms

lottie.min.js

lottie.min.js

267 ms

api.js

api.js

235 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

152 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

153 ms

wp-polyfill.min.js

wp-polyfill.min.js

155 ms

index.js

index.js

150 ms

ivory-search.min.js

ivory-search.min.js

121 ms

ivory-ajax-search.min.js

ivory-ajax-search.min.js

123 ms

fbevents.js

fbevents.js

241 ms

gtm.js

gtm.js

294 ms

logo.png

logo.png

120 ms

module-white-gold.png

module-white-gold.png

125 ms

8node.png

8node.png

124 ms

IR_Blaster-removebg-preview.png

IR_Blaster-removebg-preview.png

128 ms

admin-ajax.png

admin-ajax.png

123 ms

device-1.webp

device-1.webp

124 ms

device-2.webp

device-2.webp

129 ms

device-3.webp

device-3.webp

199 ms

device-4.webp

device-4.webp

190 ms

entertainment-device-4.jpg

entertainment-device-4.jpg

199 ms

entertainment-device-2.jpg

entertainment-device-2.jpg

188 ms

Screenshot-2022-10-23-at-11.20.50-AM.png

Screenshot-2022-10-23-at-11.20.50-AM.png

253 ms

entertainment-device-3.jpg

entertainment-device-3.jpg

196 ms

pert-lines-1.png

pert-lines-1.png

231 ms

-W__XJnvUD7dzB26Zw.ttf

-W__XJnvUD7dzB26Zw.ttf

234 ms

-W_8XJnvUD7dzB2Cy_g4bg.ttf

-W_8XJnvUD7dzB2Cy_g4bg.ttf

284 ms

-W_8XJnvUD7dzB2Cv_44bg.ttf

-W_8XJnvUD7dzB2Cv_44bg.ttf

287 ms

-W_8XJnvUD7dzB2C2_84bg.ttf

-W_8XJnvUD7dzB2C2_84bg.ttf

251 ms

Untitled_design__46_-removebg-preview.png

Untitled_design__46_-removebg-preview.png

230 ms

Untitled_design__48_-removebg-preview.png

Untitled_design__48_-removebg-preview.png

231 ms

Untitled_design__50_-removebg-preview.png

Untitled_design__50_-removebg-preview.png

231 ms

house.png

house.png

293 ms

touch-bg-1.jpg

touch-bg-1.jpg

280 ms

touch-bg-2.jpg

touch-bg-2.jpg

277 ms

touch-bg-3.jpg

touch-bg-3.jpg

283 ms

elem-2.png

elem-2.png

276 ms

Untitled-design-61.png

Untitled-design-61.png

280 ms

Untitled-design-55-1.png

Untitled-design-55-1.png

282 ms

Untitled-design-58.png

Untitled-design-58.png

283 ms

Untitled-design-60.png

Untitled-design-60.png

282 ms

install.svg

install.svg

280 ms

no-wire.svg

no-wire.svg

263 ms

modular.svg

modular.svg

266 ms

voice.svg

voice.svg

266 ms

elem-3.png

elem-3.png

269 ms

smart-house.png

smart-house.png

268 ms

New-Home-Blog-Banner-1-min.png

New-Home-Blog-Banner-1-min.png

373 ms

post-4.png

post-4.png

268 ms

arc2445_Modern_Living_Room_Villa_High_Cielings_Down_Lights_Spot_adcfe23e-32e1-47c4-bee8-686f9a1ad5f2.png

arc2445_Modern_Living_Room_Villa_High_Cielings_Down_Lights_Spot_adcfe23e-32e1-47c4-bee8-686f9a1ad5f2.png

366 ms

footer-hand.png

footer-hand.png

259 ms

sm.25.html

sm.25.html

82 ms

eso.D0Uc7kY6.js

eso.D0Uc7kY6.js

149 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDNp8A.ttf

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDNp8A.ttf

174 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTajNp8A.ttf

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTajNp8A.ttf

177 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT6jRp8A.ttf

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT6jRp8A.ttf

173 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT0zRp8A.ttf

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT0zRp8A.ttf

174 ms

convert-img.png

convert-img.png

286 ms

logo.png

logo.png

179 ms

linkdin.svg

linkdin.svg

273 ms

facebook.svg

facebook.svg

273 ms

twitter.svg

twitter.svg

273 ms

instagram-2.svg

instagram-2.svg

273 ms

youtube.svg

youtube.svg

273 ms

recaptcha__en.js

recaptcha__en.js

143 ms

anchor

anchor

37 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

12 ms

tE6BD2dmJ4MsSW_XgLndBgqWpAgx-dXQ3y0tInp2GOI.js

tE6BD2dmJ4MsSW_XgLndBgqWpAgx-dXQ3y0tInp2GOI.js

43 ms

webworker.js

webworker.js

42 ms

logo_48.png

logo_48.png

29 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

9 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

10 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

9 ms

recaptcha__en.js

recaptcha__en.js

60 ms

Accessibility Review

pert.me accessibility score

84

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

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

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

pert.me 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pert.me SEO score

100

Search Engine Optimization Advices

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 Pert.me 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 Pert.me 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

pert.me

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