Tools & Wizards About Us
ifull.my screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    33% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 99

    SEO

    Google-friendlier than
    94% of websites

ifull.my

iFull:Best Smart phone,iPhone iPad Repair Malaysia With Warranty

Page Load Speed

10.6 sec in total

First Response

3.4 sec

Resources Loaded

6.8 sec

Page Rendered

334 ms

ifull.my screenshot

About Website

Welcome to ifull.my homepage info - get ready to check IFull best content right away, or after learning these important things about ifull.my

Doorstep Instant Smartphones, iPad iPhone Repair Malaysia including Battery replacement, LCD screen repair.Trained Technician,Repair in 30min, No data loss.

Visit ifull.my

Key Findings

We analyzed Ifull.my page load time and found that the first response time was 3.4 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

ifull.my performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,570 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

ifull.my

3444 ms

wp-emoji-release.min.js

413 ms

style.min.css

709 ms

mainstyles.css

484 ms

styles.css

491 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 80% of them (85 requests) were addressed to the original Ifull.my, 8% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Ifull.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.7 kB (20%)

Content Size

259.5 kB

After Optimization

208.8 kB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Ifull.my main page is 259.5 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. 65% of websites need less resources to load. Javascripts take 129.3 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-1%

Potential reduce by 15 B

  • Original 2.1 kB
  • After minification 2.1 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. IFull images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 16.9 kB

  • Original 129.3 kB
  • After minification 129.3 kB
  • After compression 112.4 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 16.9 kB or 13% of the original size.

CSS Optimization

-26%

Potential reduce by 33.8 kB

  • Original 128.2 kB
  • After minification 128.0 kB
  • After compression 94.4 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. Ifull.my needs all CSS files to be minified and compressed as it can save up to 33.8 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 74 (90%)

Requests Now

82

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ifull.my

ifull.my

3444 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

413 ms

style.min.css

style.min.css

709 ms

mainstyles.css

mainstyles.css

484 ms

styles.css

styles.css

491 ms

jquery-ui.min.css

jquery-ui.min.css

15 ms

jquery-ui-timepicker-addon.min.css

jquery-ui-timepicker-addon.min.css

496 ms

settings.css

settings.css

504 ms

reset.css

reset.css

640 ms

superfish.css

superfish.css

725 ms

prettyPhoto.css

prettyPhoto.css

734 ms

jquery.qtip.css

jquery.qtip.css

743 ms

odometer-theme-default.css

odometer-theme-default.css

754 ms

animations.css

animations.css

869 ms

style.css

style.css

941 ms

css

css

27 ms

style.css

style.css

965 ms

responsive.css

responsive.css

976 ms

styles.css

styles.css

990 ms

styles.css

styles.css

1003 ms

styles.css

styles.css

1096 ms

styles.css

styles.css

1178 ms

custom.css

custom.css

1205 ms

js_composer.min.css

js_composer.min.css

1705 ms

style.css

style.css

1236 ms

css

css

23 ms

css

css

24 ms

style.css

style.css

1253 ms

responsive.css

responsive.css

1322 ms

jquery.min.js

jquery.min.js

1411 ms

jquery-migrate.min.js

jquery-migrate.min.js

1443 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1991 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1504 ms

js

js

54 ms

app.js

app.js

1384 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1480 ms

wp-polyfill.min.js

wp-polyfill.min.js

1518 ms

hooks.min.js

hooks.min.js

1642 ms

i18n.min.js

i18n.min.js

1643 ms

lodash.min.js

lodash.min.js

1767 ms

url.min.js

url.min.js

1821 ms

datepicker-en-GB.min.js

datepicker-en-GB.min.js

5 ms

api-fetch.min.js

api-fetch.min.js

1927 ms

index.js

index.js

1703 ms

core.min.js

core.min.js

1631 ms

datepicker.min.js

datepicker.min.js

1646 ms

jquery-ui-timepicker-addon.min.js

jquery-ui-timepicker-addon.min.js

1731 ms

jquery-ui-timepicker-en-GB.js

jquery-ui-timepicker-en-GB.js

1732 ms

mouse.min.js

mouse.min.js

1598 ms

slider.min.js

slider.min.js

1544 ms

controlgroup.min.js

controlgroup.min.js

1552 ms

checkboxradio.min.js

checkboxradio.min.js

1636 ms

button.min.js

button.min.js

1724 ms

jquery-ui-sliderAccess.js

jquery-ui-sliderAccess.js

1728 ms

accordion.min.js

accordion.min.js

1618 ms

tabs.min.js

tabs.min.js

1538 ms

menu.min.js

menu.min.js

1564 ms

selectmenu.min.js

selectmenu.min.js

1629 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

1719 ms

jquery.isotope.min.js

jquery.isotope.min.js

1721 ms

jquery.ba-bbq.min.js

jquery.ba-bbq.min.js

1614 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

1555 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

1576 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

1604 ms

jquery.transit.min.js

jquery.transit.min.js

1695 ms

jquery.hint.min.js

jquery.hint.min.js

1613 ms

jquery.qtip.min.js

jquery.qtip.min.js

1555 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1533 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

1525 ms

main.js

main.js

1522 ms

odometer.min.js

odometer.min.js

1519 ms

jquery.costCalculator.min.js

jquery.costCalculator.min.js

1501 ms

cost_calculator.js

cost_calculator.js

1401 ms

js_composer_front.min.js

js_composer_front.min.js

1415 ms

analytics.js

analytics.js

112 ms

jquery-ui-tabs-rotate.min.js

jquery-ui-tabs-rotate.min.js

1423 ms

forms.min.js

forms.min.js

1371 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

49 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

43 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

39 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

43 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

48 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

41 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

48 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

43 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

43 ms

collect

collect

122 ms

social.ttf

social.ttf

1406 ms

streamline-small.woff

streamline-small.woff

1334 ms

collect

collect

42 ms

streamline-large.woff

streamline-large.woff

1384 ms

template.woff

template.woff

1387 ms

v3.png

v3.png

685 ms

IFULL-WEB-BANNER-e1549904302739.png

IFULL-WEB-BANNER-e1549904302739.png

666 ms

1a-01-e1549905705654.png

1a-01-e1549905705654.png

579 ms

iphone6-150x150.png

iphone6-150x150.png

570 ms

ipadpro10_wifigold-150x150.png

ipadpro10_wifigold-150x150.png

568 ms

Huawei-Mate-9-150x150.png

Huawei-Mate-9-150x150.png

553 ms

DSC_0309-1-480x480.jpg

DSC_0309-1-480x480.jpg

530 ms

Artboard-1-90x90.png

Artboard-1-90x90.png

435 ms

Artboard-8-90x90.png

Artboard-8-90x90.png

338 ms

e1-01-e1549902879655.png

e1-01-e1549902879655.png

324 ms

overlay.png

overlay.png

1074 ms

ui-bg_glass_65_ffffff_1x400.png

ui-bg_glass_65_ffffff_1x400.png

25 ms

ui-bg_glass_75_e6e6e6_1x400.png

ui-bg_glass_75_e6e6e6_1x400.png

4 ms

1f642.svg

1f642.svg

17 ms

Accessibility Review

ifull.my accessibility score

87

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

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

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

ifull.my 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ifull.my SEO score

99

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifull.my can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ifull.my 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

ifull.my

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